Two-way sync
Changes in SQL Server or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep SQL Server 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 SQL Server'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 SQL Server where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in SQL Server sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into SQL Server, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Starburst Enterprise sync into SQL Server, 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 Starburst Enterprise and keep SQL Server 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.
| SQL Server objects | Starburst Enterprise objects | |
|---|---|---|
| Tables The primary sync target; rows map to records in connected systems. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Views Read-side projections used as outbound sync sources. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Columns Field-level mapping targets with T-SQL types. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Stored Procedures T-SQL logic that can validate or post-process synced rows. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SQL Server–Starburst Enterprise connection.
Changes in SQL Server or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever SQL Server 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 SQL Server or Starburst Enterprise record.
Track your SQL Server ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between SQL Server 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 SQL Server 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 SQL Server 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 SQL Server and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as SQL Server's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Starburst Enterprise side: Materialized views, Columns, Catalogs, Schemas, plus custom fields where Starburst Enterprise exposes them. On the SQL Server side: Views, Columns, Primary and Unique Keys, CDC Change 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 SQL Server and Starburst Enterprise: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in Starburst Enterprise sync into SQL Server, where whatever reads from that database gets them without querying the warehouse.
SQL Server: SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers. Authentication: Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page. 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.
Starburst Enterprise: It is built on open-source Trino, so Trino drivers, clients, and SQL semantics apply. SQL Server: Native Change Data Capture reads inserts, updates, and deletes from the transaction log into change tables without touching application code. Stacksync's field mapping accounts for these differences between SQL Server and Starburst Enterprise 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 SQL Server and Starburst Enterprise.