Executive summary
A global dashboard is a business requirement, not necessarily a mandate to put every country’s raw data into one warehouse region. Google BigQuery global queries, currently a Preview feature, allow SQL to reference tables stored in multiple BigQuery locations. They can simplify selected cross-region joins and reporting without a permanent, manually managed replica of every source dataset. The trade-off is fundamental: the query engine still moves selected data between regions to execute the result. That movement creates residency, security, cost, performance and operating-model questions that should be answered before an executive dashboard depends on it.
The decision is not simply ‘centralize or federate.’ Most mature multinational platforms need a deliberate mix: regional source-of-truth datasets, approved cross-region queries for occasional analysis, and selectively materialized regional or central reporting marts for high-frequency use. Start with what the business must compare, what is legally and contractually permitted to cross borders, how fresh the numbers must be, and who owns the costs and exceptions. Then choose the least complex architecture that meets those constraints.
What BigQuery global queries actually do
BigQuery’s global-query capability lets one SQL statement reference datasets located in different regions. For example, an organization could compare European and US product sales using a UNION ALL or join a small regional product dimension to another region’s transaction table. The feature does not turn geographically separate datasets into one physically co-located store. BigQuery selects a primary execution location, runs remote subqueries, transfers the results needed for final processing, temporarily stores copied data in the primary location and completes the query there.
Google’s global queries documentation describes temporary tables in the primary location that persist for 24 hours, with possible reuse of smaller remote-subquery results. This is an important distinction for governance reviews: avoiding an ETL pipeline does not mean avoiding cross-border data copies, even if those copies are temporary. The documented implementation can change while the feature remains in Preview, so teams should confirm current behavior and contract terms before production approval.
The relevant question for leaders is therefore not ‘Can SQL see both regions?’ It is ‘What exact fields and rows leave each region, for how long, under whose permissions, and with what business justification?’ A successful proof of concept should answer those questions using job evidence rather than assumptions about the optimizer.

Three architecture choices, and when each makes sense
1. Keep reporting entirely regional
Run transformations and dashboards in the same geography as the data. This is the default for datasets that cannot leave a jurisdiction, regulated workloads with strict processing-location controls, or reports used only by a regional team. It avoids cross-region transfer for the report itself, although metadata, access paths and downstream exports still need separate review. The limitation is that global executives may receive comparable regional metrics only after an additional approved aggregation step.
2. Use global queries selectively
Use global queries when the business needs occasional cross-region comparisons, data is permitted to move, the data volume after remote filtering is modest, and a short delay is acceptable. Examples include an analyst comparing a few countries’ product-category totals, a quarterly finance reconciliation or a limited cross-region reference-data join. The advantage is fewer permanent replicas and potentially less pipeline maintenance. The disadvantages are Preview risk, variable latency, additional charges and the possibility of transferring more data than the SQL author expected.
3. Replicate or materialize approved reporting data
For frequently refreshed executive dashboards, predictable service-level objectives or large repeated joins, consider producing regionally approved aggregates and moving only those into a reporting mart. This adds an ingestion or replication process and explicit ownership, but can provide stable dashboard latency, repeatable costs and better control over the published metric contract. A selective aggregate is often a better governance outcome than copying every underlying customer-level record.
These are not mutually exclusive. A platform may keep personally identifiable data regional, distribute a small standardized product dimension, publish country-level KPI tables centrally, and retain global queries for governed ad hoc investigations. A sound architecture review should evaluate all four data paths independently.
The data-residency question comes before SQL
Data residency is not determined solely by where the original BigQuery table is stored. Global queries copy data from remote regions into the execution region. A dataset can remain physically in Europe while selected European rows are temporarily copied to the United States for a cross-region query. If a contract, internal policy or legal obligation restricts transfer or processing, that query may be unacceptable even though no persistent cross-region ETL job exists.
Create a data-movement register for each proposed workload. Record source region, destination execution region, dataset owner, field classification, purpose, authorized recipients, retention expectations, encryption requirements and whether row-level or column-level controls apply. Do not infer that a platform feature automatically satisfies GDPR, financial-sector rules, healthcare requirements or sovereign-cloud policies. Legal and security owners must determine which rules apply to the particular data, organization and transfer mechanism.

When the requirement is ‘data from country X must never leave country X,’ do not rely on an SQL WHERE clause as the primary policy control. Deny cross-region access for that source and use regional reporting or a separately approved disclosure process. Where transfers are permitted only for aggregates, compute those aggregates in-region and publish the approved output. Aggregation can reduce exposure but is not inherently anonymization; small cohorts, dimensions and repeated queries can still reveal sensitive information.
Global queries are not supported in BigQuery Assured Workloads according to Google’s current documentation, and regional endpoints are also unsupported. This is a practical go/no-go test, not an issue to discover after development. Security teams should review temporary tables, customer-managed encryption key behavior and audit coverage as part of approval.
Choose the execution region deliberately
BigQuery can choose a location automatically if none is specified. For ordinary SELECT queries, the documented location may be selected from referenced datasets rather than from the place the report consumer sits. That is too ambiguous for a governed multinational workload. Set the execution location explicitly, document why it is approved, and test which region performs the final aggregation.
The preferred execution location is not always headquarters. It is usually the permitted region that minimizes transferred data while providing adequate compute capacity. If one region contains a large fact table and another contains a small dimension, it may be cheaper and faster to move the filtered dimension toward the fact table. If the organization requires the final result to remain in the EU, that governance constraint takes precedence over a purely financial optimization.
Capacity is also regional. The selected execution location determines where the final query consumes BigQuery slots or on-demand compute, while remote subqueries consume resources in their own regions. Evaluate reservation assignments and regional service-level objectives before promising a single global dashboard refresh time.
A practical SQL pattern for a controlled pilot
The following is an illustrative query structure, not a tested deployment script. Replace project IDs, dataset names and column names with your actual resources, confirm the referenced tables are in different BigQuery locations, and obtain the required global-query configuration and permissions first.
SET @@location = ‘EU’;
SELECT region_code, report_month, SUM(net_revenue) AS net_revenue
FROM (
SELECT ‘EU’ AS region_code, report_month, net_revenue
FROM `example-eu.finance_reporting.monthly_sales`
WHERE report_month >= DATE ‘2026-01-01’
UNION ALL
SELECT ‘US’ AS region_code, report_month, net_revenue
FROM `example-us.finance_reporting.monthly_sales`
WHERE report_month >= DATE ‘2026-01-01’
)
GROUP BY region_code, report_month
ORDER BY report_month, region_code;
This example assumes the two sources are already approved reporting tables rather than unrestricted transaction records. The EU execution location is explicit; the US source may be copied to the EU as part of the global query. The example is inappropriate where policy prohibits that transfer. The purpose of the pilot is to compare measured transfer, cost and latency with an alternative that materializes approved monthly aggregates ahead of time.
For cross-region joins, filter early and select only required columns. Google’s documentation describes remote predicate and projection pushdowns, but does not guarantee them for every query. Certain structures, including queries referencing STRUCT columns, can prevent remote pushdowns. Inspect actual remote jobs and copied bytes before assuming the engine moved only a small subset.
Permissions and project-level controls
Global queries require explicit configuration. The project executing the query must enable global-query execution in the primary region. The project holding a remote table must allow global-query data access from its region. These are separate controls and can apply across projects. Treat enabling them as a controlled infrastructure change with an owner, an approval record, a rollback procedure and periodic review.
Google documents a specific bigquery.jobs.createGlobalQuery permission. Its current guidance says the BigQuery Admin predefined role contains it, and recommends a custom role for selected users or service accounts that need global-query execution without broad administration privileges. Existing dataset and table permissions still matter. Avoid granting general administrator access simply to make an experimental dashboard work.
Segregate production service accounts from ad hoc analyst identities. Restrict who may enable execution, who may permit source-region access, and who may run cross-region jobs. Keep a register of allowed region pairs and permitted datasets. Consider disabling global queries at the project or organization level in regions where movement is not approved. The capability to execute a query is not a substitute for permission to transfer its data.
Understand the real cost: four components, not one
The price of a global query is not merely the amount of data scanned by the final SELECT. Google’s documentation identifies four components: remote-region subquery compute, primary-region final-query compute, inter-region data replication charges, and temporary storage charges for copied data. The amounts depend on location, pricing model, query structure, frequency and the volume actually transferred.
Build a cost model for each candidate report: monthly run count × average remote compute cost, plus monthly primary compute, plus bytes copied × the applicable region-pair transfer rate, plus temporary storage. Add engineering and operational costs when comparing with a materialized alternative. Do not insert generic dollar-per-gigabyte assumptions into a business case without checking the actual region-pair prices and contractual discounts.

An illustrative break-even exercise: suppose a dashboard runs 48 times a day and each run transfers a filtered 4 GB from a remote region. That is 192 GB of cross-region movement per day before retries or any caching benefit. At 30 days, the theoretical total is 5.76 TB. This is a volume illustration, not a price estimate and not a claim about BigQuery’s actual caching for that workload. If the business only needs daily totals, a once-daily 50 MB approved aggregate might materially change the economics. Test both approaches with the same output and freshness requirements.
A query that fails after cross-region replication may still incur replication charges because global queries are not atomic. Build this into retry budgets and alerting. Quotas also apply: Google’s published limits include per-region-pair transfer, per-copy-job transfer and per-project copy-job counts. Check the current BigQuery quotas and limits before assuming a design can scale from a small pilot to enterprise-wide usage.
Performance: measure the user experience, not just SQL runtime
Cross-region execution adds network movement and remote-stage dependencies. A dashboard that refreshes in two seconds with co-located data may not meet the same latency when it repeatedly coordinates remote subqueries and temporary copies. Test p50 and p95 end-to-end refresh time, not only the BigQuery job’s reported duration. Include semantic-layer queries, BI-tool concurrency, caching behavior, authentication and downstream visualization time.
Design representative tests around a small query, a broad scan, a filtered join, a recurring executive dashboard and a concurrent month-end workload. For each, record bytes scanned by region, bytes transferred, remote job count, primary slot consumption, elapsed time, failure rate and cost. Compare these with a regional-aggregate mart using identical metric definitions.
Do not overgeneralize from one fast test. Query plans can change with data distributions and SQL shape. A remote filter may be pushed down in one query and not another. The platform may reuse a small temporary result under documented conditions, but your operating model should not depend on unverified cache hit rates. A conservative production design assumes it can pay the transfer cost again.
Monitoring and auditability across regions
A single parent job does not tell the whole operational story. Google’s documentation describes remote child jobs, cross-region copy jobs and global-query metadata in the jobs API, audit logs and INFORMATION_SCHEMA.JOBS. The parent job exposes remote regions; child jobs identify their parent. Build observability that can connect these records to the dashboard or application that initiated the query.
At minimum, track parent job ID, principal, source and execution regions, report name, query hash, remote bytes copied, remote and primary compute, total duration, errors, retries and policy approval. Add cost attribution by business unit and alert when a new region pair appears. The query execution graph alone may not show copied bytes, so include the copy-job records from job history.

A useful monitoring question is: ‘Which five dashboards caused the most cross-region movement this week, and did any transfer involve a newly classified dataset?’ That is more actionable than a single monthly cloud invoice. It also creates evidence for periodic governance reviews and future decisions to replace repeated remote joins with approved materialized summaries.
Reporting correctness is a separate risk
Global queries do not automatically give a consistent global reporting cutoff. Regional source tables may load on different schedules, use different local business calendars or apply different exchange rates and return rules. A query can run successfully while comparing US sales through 23:00 UTC with European sales through 18:00 UTC. The problem is semantic and operational, not SQL syntax.
Define a reporting contract before integrating data: reporting currency, exchange-rate source and effective date, timezone conversion, transaction recognition rules, fiscal calendar, handling of late events, refunds, deduplication and source refresh watermark. Include a field that tells users how current each regional input is. For executive dashboards, publish the last successfully reconciled period rather than silently mixing fresh and stale data.
Automated tests should compare regional subtotals with the approved source reports, verify row counts and duplicate keys, and detect missing regions. Actiknow’s article on BigQuery pipeline unit testing offers a complementary way to validate transformation logic before it reaches executive dashboards. Unit tests do not replace cross-region reconciliation, but they reduce the chance that a simple SQL change breaks an otherwise well-governed report.
Decision matrix: when to choose each pattern
Choose regional-only reporting when: policy forbids movement; data is highly sensitive; local users are the primary consumers; or a compliant central aggregate is not yet defined.
Choose selective global queries when: transfers are approved; queries are occasional; remote results are small after filtering; latency can vary; and a Preview dependency is acceptable.
Choose approved aggregate replication when: a global KPI must refresh predictably; queries repeat often; the data contract is stable; or leadership needs a low-cost, low-latency dashboard.
Choose broader replication only when: repeated detailed analysis genuinely requires it, retention and access controls are approved, and the ongoing ingestion and governance costs are justified.
Use a weighted scorecard rather than a tool preference. Score each design from 1 to 5 for compliance fit, business freshness, p95 latency, monthly run cost, operational burden, auditability and reversibility. Compliance can be a hard gate instead of a weighted factor: an otherwise cheap architecture should not pass if it violates an approved data-location restriction.
A four-week pilot plan
Week 1: inventory and permission boundaries
Choose one high-value report spanning exactly two regions. Identify its data owners, classifications, region pair, row volumes, dashboard users and refresh requirement. Confirm Preview acceptance, service availability, Assured Workloads restrictions, key-management controls and data-transfer approvals. Capture the current report’s baseline accuracy, cost and refresh time. Document a no-transfer fallback.
Week 2: build two comparable implementations
Implement a global query using approved fields and explicit execution location. Separately create a small approved aggregate mart, populated on an agreed schedule. Use the same business definitions and test inputs for both. Configure a narrowly scoped execution identity and document the project-level options. Do not grant access to all regional datasets just to simplify the pilot.
Week 3: load, cost and failure testing
Run both designs across typical and peak data volumes, multiple BI users and controlled failure conditions. Inspect remote child jobs and copy jobs; measure transferred bytes rather than estimating them from source-table size. Reconcile each regional subtotal. Test missing-source handling, a late-arriving batch, cancellation, retries and temporary unavailability. Review actual billed usage with the cloud finance owner.
Week 4: decision and operating handoff
Produce a short decision record: approved region pair, use case, query and data owners, expected run frequency, measured cost per run, p95 latency, quality checks, monitoring owner, escalation process and a rollback path. Decide whether to proceed, limit to analyst use, switch to approved aggregates or retain regional reporting. Do not promote a Preview-dependent workload into a critical executive reporting path without an explicit exception and fallback.

Executive acceptance checklist
Business: One named report owner, one reconciled KPI contract, an explicit freshness objective and an agreed source-of-truth definition.
Governance: Documented transfer approval, source and destination regions, classified fields, least-privilege access and a clear prohibition mechanism for disallowed regions.
Technical: Explicit execution location, confirmed feature configuration, tested query behavior, reviewed Preview limitations and an approved fallback.
Financial: Measured remote compute, final compute, copied bytes, temporary storage, expected run count and alert thresholds.
Operational: Region-aware job monitoring, data-quality checks, failure handling, ownership of changes and periodic access review.
Frequently asked questions
1. Are BigQuery global queries generally available?
As of the Google documentation reviewed on 10 November 2026, global queries are labeled Preview. Treat support commitments and feature behavior accordingly, and recheck the current release status before making a long-term platform commitment.
2. Does a global query leave data in its original region?
The source table remains in its region, but data required for the query can be copied to the primary execution region and stored temporarily. The feature is not a zero-movement federation guarantee.
3. Can global queries replace all ETL and ELT pipelines?
No. They can remove some manual cross-region replication for selected queries. They do not solve source ingestion, metric standardization, quality assurance, history management, dashboard performance or legal transfer approval.
4. Can a team choose where a global query runs?
Yes. Set an explicit execution location and confirm that project settings and permissions allow it. Avoid relying on automatic location selection for workloads with residency or cost requirements.
5. Are global queries suitable for regulated data?
Only after a workload-specific security, legal and contractual review. Certain deployments, including Assured Workloads, are not supported by the feature. Data classification and transfer restrictions may rule out particular region pairs.
6. What makes global queries more expensive than local queries?
Potential charges include remote compute, primary-region compute, inter-region replication and temporary storage. Repeated queries, broad remote scans and failed jobs can increase costs.
7. Can BigQuery reduce the amount of data moved?
It can push selected filters and projections into remote subqueries. Pushdown depends on query shape, so validate actual transfer using child and copy jobs. Some structures, including references to STRUCT columns, can prevent pushdown.
8. Do global queries work with materialized views?
Google currently lists materialized views over global queries as unsupported. For recurring dashboards, consider a separately managed reporting mart or a regional aggregate pipeline instead.
9. What permission is required?
The documentation identifies bigquery.jobs.createGlobalQuery. Use a custom role where appropriate, together with normal source-data permissions and controlled project-level enablement.
10. How should we monitor cross-region queries?
Link parent jobs to remote subqueries and copy jobs using job history, the jobs API, audit logs and INFORMATION_SCHEMA. Monitor source regions, transferred bytes, cost, errors, latency and the responsible report.
11. How do global queries differ from BigQuery Omni?
Global queries address BigQuery datasets stored in different BigQuery regions. BigQuery Omni is a separate cross-cloud capability for querying data associated with other cloud environments. Their supported sources, execution paths, limits and pricing should be evaluated independently.
12. What is the safest first use case?
A low-frequency, non-sensitive, two-region report with small approved aggregates, clear data ownership and an existing regional baseline. This makes it easier to verify movement, reconcile numbers and reverse the decision.
Final recommendation
Do not centralize multinational reporting by default, and do not reject cross-region SQL simply because data lives in more than one region. First define the decision, residency boundary, freshness requirement and cost tolerance. Then pilot global queries against a selective aggregate architecture using measured transfers and reconciled outputs. For most leadership dashboards, a governed regional-data-plus-approved-aggregate model remains the more predictable baseline, while global queries can be a useful controlled option for exploratory analysis.
Actiknow’s business intelligence consulting and data integration services cover requirements, architecture, data modeling and dashboards, while its cloud application development practice includes Google Cloud and BigQuery-related work. If your team is deciding between regional reporting, selective cross-region SQL and a central reporting mart, contact Actiknow to discuss a scoped architecture assessment and pilot.
Further reading and source verification
Google Cloud’s official global queries guide documents Preview status, enablement, execution behavior, temporary data movement, permissions, costs and limitations. The BigQuery quotas and limits reference lists relevant transfer and copy-job constraints. Product behavior and quotas can change; review these sources again before deployment.
Editorial note: This article is architectural guidance, not legal advice or a claim of measured customer outcomes. Illustrative SQL, cost volumes and implementation timelines are examples, not evidence of an Actiknow client deployment.

