Skip to content
Database ⇄ Data warehouse

MySQL to Starburst Enterprise integration — real-time, two-way sync

Keep MySQL 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MySQL and Starburst Enterprise

Connect MySQL and Starburst Enterprise with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want MySQL'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 MySQL where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in MySQL sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into MySQL, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 02 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 03 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
  • 04 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts

Common sync patterns

Operational data in the warehouse, minus the pipeline

Rows from MySQL land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Starburst Enterprise sync into MySQL, where whatever reads from that database gets them without querying the warehouse.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

What you can sync between MySQL and Starburst Enterprise

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.

MySQL objects Starburst Enterprise objects How this pairing syncs
Tables The primary sync target; rows map to records in connected systems. Tables Queryable relations; writes pass through to sources whose connectors support them. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Read-side projections used as outbound sync sources. Views Engine-level SQL views used to shape federated data before syncing it out. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Columns Field-level mapping targets with engine-typed values. Columns Typed per the Trino type system, mapped from each source's native types. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Triggers An alternative change-capture mechanism when binlog access is unavailable. Materialized views Precomputed results that make repeated sync reads cheaper. Triggers is specific to MySQL and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Databases (Schemas) is specific to MySQL and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Primary and Unique Keys is specific to MySQL and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between MySQL and Starburst Enterprise

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

MySQL Starburst Enterprise Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise MySQL Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with MySQL ⇄ Starburst Enterprise

Connect MySQL and Starburst Enterprise for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Starburst Enterprise connection.

Real-time

Two-way sync

Changes in MySQL or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MySQL or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single MySQL or Starburst Enterprise record.

Observability

Monitoring

Track your MySQL ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MySQL and Starburst Enterprise.

How the MySQL and Starburst Enterprise connectors work

MySQL

Integration surface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL setup guide

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect MySQL to Starburst Enterprise — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate MySQL 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MySQL connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MySQL 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MySQL ⇄ Starburst Enterprise
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    MySQL Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MySQL and Starburst Enterprise integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 476 integrations available for MySQL and Starburst Enterprise.

Popular · 5 of 476
All MySQL integrations All Starburst Enterprise integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own