Two-way sync
Changes in Google Cloud SQL or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud SQL 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.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Google Cloud SQL's rows in Starburst Enterprise, 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 SQL 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 SQL sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into Google Cloud SQL, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Starburst Enterprise and keep Google Cloud SQL focused on its operational workload.
Rows from Google Cloud SQL land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
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.
| Google Cloud SQL objects | Starburst Enterprise objects | |
|---|---|---|
| Transaction logs MySQL binlog or PostgreSQL WAL, the source for log-based change capture. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Instances The managed MySQL, PostgreSQL, or SQL Server server a sync connects to. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Databases Scope the tables included in a sync configuration. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Schemas Namespace tables in PostgreSQL and SQL Server instances. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Tables Mapped directly to sync targets; schema changes can be propagated. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Rows Read and written by primary key during each sync cycle. | Materialized views Precomputed results that make repeated sync reads cheaper. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud SQL–Starburst Enterprise connection.
Changes in Google Cloud SQL or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud SQL 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 Google Cloud SQL or Starburst Enterprise record.
Track your Google Cloud SQL ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Google Cloud SQL's Transaction logs and Instances), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Google Cloud SQL and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Google Cloud SQL: Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking; polling as a fallback. 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 Starburst Enterprise side: Catalogs, Schemas, Tables, Views, plus custom fields where Starburst Enterprise exposes them. On the Google Cloud SQL side: Rows, Views, Transaction logs, Instances. 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 Google Cloud SQL and Starburst Enterprise: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
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 Google Cloud SQL and Starburst Enterprise.