Skip to content
Data warehouse

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

Keep Databricks 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 Databricks and Starburst Enterprise

Keep tables consistent across Databricks and Starburst Enterprise, for a migration, a multi-warehouse stack, or a dataset two platforms both need.

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 Databricks 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.

Common use cases

  • 01 Serve ML feature outputs computed in Databricks to production apps through a synced operational store.
  • 02 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
  • 03 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 04 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first

Common sync patterns

Migration without a big bang

When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.

Serve tools that only connect to one platform

Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.

Shared datasets across teams

Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.

What you can sync between Databricks 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.

Databricks objects Starburst Enterprise objects How this pairing syncs
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Schemas Group tables and views; syncs typically target a dedicated schema per source system. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Curated read-only projections used as sync sources for downstream tools. 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.
Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. Materialized views Precomputed results that make repeated sync reads cheaper. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Delta Tables The primary read and write target; operational data lands here as managed or external tables. Tables Queryable relations; writes pass through to sources whose connectors support them. Delta Tables is specific to Databricks and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
Volumes Unity Catalog file storage used for staging bulk loads. Columns Typed per the Trino type system, mapped from each source's native types. Volumes is specific to Databricks and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Databricks 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.

Databricks Starburst Enterprise Sub-second propagation

DetectionChanges in Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.

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

Starburst Enterprise Databricks 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 Databricks as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Databricks: Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Databricks ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Databricks 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 Databricks or Starburst Enterprise record.

Observability

Monitoring

Track your Databricks ⇄ 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 Databricks and Starburst Enterprise.

How the Databricks and Starburst Enterprise connectors work

Databricks

Integration surface
SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
Authentication
Personal access tokens or OAuth machine-to-machine credentials for service principals
Change detection
Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
Capabilities
read · write · CDC
Rate limits
Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits

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 Databricks 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 Databricks 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
    Databricks connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Databricks 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 · Databricks ⇄ 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
    Databricks Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Databricks 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.

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:

Related integrations

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

Popular · 6 of 480
Coworkers laughing in front of a laptop in a casual office setting

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