Two-way sync
Changes in BigQuery or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and Google Cloud Spanner in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Google Cloud Spanner's rows in BigQuery, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Google Cloud Spanner where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Google Cloud Spanner sync into BigQuery in real time, and result tables in BigQuery sync back into Google Cloud Spanner, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in BigQuery sync into Google Cloud Spanner, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in BigQuery and keep Google Cloud Spanner focused on its operational workload.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| BigQuery objects | Google Cloud Spanner objects | |
|---|---|---|
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Secondary indexes Used to make incremental read queries efficient on non-key columns. | |
| Clustered tables Supported; clustering is transparent to the sync. | Change streams Capture inserts, updates, and deletes for log-style change data capture. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Views Read-only projections useful for shaping data before it leaves Spanner. | |
| Projects Connection scope: the service account grants access per project. | Databases Top-level containers that scope schema and sync configuration. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Tables Relational tables mapped one-to-one to sync targets. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Google Cloud Spanner connection.
Changes in BigQuery or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Google Cloud Spanner data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or Google Cloud Spanner record.
Track your BigQuery ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Google Cloud Spanner.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate BigQuery and Google Cloud Spanner with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the BigQuery and Google Cloud Spanner objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BigQuery and Google Cloud Spanner: authenticate both systems, choose the objects to sync (such as BigQuery's Partitioned tables and Clustered tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the BigQuery side: Datasets, Projects, Tables, Partitioned tables, plus custom fields where BigQuery exposes them. On the Google Cloud Spanner side: Databases, Tables, Rows, Interleaved tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for BigQuery and Google Cloud Spanner: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in BigQuery sync into Google Cloud Spanner, where whatever reads from that database gets them without querying the warehouse.
BigQuery: GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs. Authentication: Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver. Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: BigQuery is serverless: there are no clusters or warehouses to size, and storage and compute are billed separately. Google Cloud Spanner: It supports two SQL dialects: GoogleSQL and a PostgreSQL-interface dialect chosen at database creation. Stacksync's field mapping accounts for these differences between BigQuery and Google Cloud Spanner without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for BigQuery and Google Cloud Spanner.