Two-way sync
Changes in BigQuery or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.
Stacksync syncs tables between BigQuery and Starburst Enterprise continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.
Bring the acquired company's warehouse data across continuously instead of through one-off dumps.
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 | Starburst Enterprise objects | |
|---|---|---|
| Datasets Organizational container — you pick which dataset’s tables to sync. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Projects Connection scope: the service account grants access per project. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Clustered tables Supported; clustering is transparent to the sync. | Views Engine-level SQL views used to shape federated data before syncing it out. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Starburst Enterprise connection.
Changes in BigQuery or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Starburst Enterprise 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 Starburst Enterprise record.
Track your BigQuery ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Starburst Enterprise.
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 Starburst Enterprise 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 Starburst Enterprise 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 Starburst Enterprise: authenticate both systems, choose the objects to sync (such as BigQuery's Datasets and Projects), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on BigQuery: Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the BigQuery side: Projects, Tables, Partitioned tables, Clustered tables, plus custom fields where BigQuery exposes them. On the Starburst Enterprise side: Catalogs, Schemas, Tables, Views. 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 Starburst Enterprise: Serve tools that only connect to one platform; Shared datasets across teams; Consolidation after M&A. Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
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. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
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 Starburst Enterprise.