BigQuery Global Queries: Join Data Across Regions Without ETL

As of February 2026, Google released BigQuery Global Queries in Preview. It lets you join tables from completely different geographic regions — say, asia-northeast1 (Tokyo) and us-central1 (Iowa) — in a single SQL statement. No ETL, no data movement pipelines, no manual copying. This post covers how it actually works under the hood, what it costs, and the gotchas you need to know before using it in production. The Old Problem BigQuery historically required all datasets referenced in a single query to live in the same location. If your sales data was in Tokyo and your user master was in the US, you had two options: Copy one dataset to the other region (ETL pipeline, operational overhead). Run two separate queries and join the results in application code. Global Queries eliminates this constraint. How It Works: 4-Stage Execution When you run a global query, BigQuery orchestrates the execution across regions transparently: 1. Distributed Execution The Query Optimizer analyzes the query, i