Docs /Basics /All BigQuery articles
BasicsBigQuery

BigQuery concepts

How BigQuery works, explained with examples you can run in the browser: 107 articles on cost, storage, SQL, writing data, scripting, performance, security and operations, checked against BigQuery.

These articles explain what is specific to BigQuery: how it bills a query, how partitioning and nested data work, which SQL behaves differently from other databases, and the limits you run into. They are based on Google's BigQuery documentation, rewritten and tested: every example on these pages was run on BigQuery, and the result you see is BigQuery's answer. On a desktop browser you can edit an example and run it on Querylab.io's BigQuery engine without an account.

New to BigQuery? Start with How BigQuery works and How a query is billed.

Basics

  • How BigQuery works BigQuery keeps storage and compute separate, stores each column on its own, and runs a query as parallel stages on slots.
  • How BigQuery SQL differs from other SQL BigQuery SQL (GoogleSQL) uses backticks for names, has no implicit string-to-number casts, only one integer type, and requires ALL or DISTINCT after UNION.
  • Projects, datasets and tables in BigQuery A BigQuery table is named project.dataset.table.
  • BigQuery locations and regions Every BigQuery dataset has one location, a region like europe-west1 or a multi-region like US or EU, and a query runs in the location of the data it reads.
  • BigQuery jobs Every query, load, export and copy in BigQuery runs as a job with an ID, a state and a project that is billed.

Cost and pricing

Tables and storage

Querying

Writing data

Scripting and routines

Views

Performance

Security and governance

Sharing

Metadata and operations

External data

AI and ML

Tools and APIs