Two-way sync
Changes in Databricks or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Keep Databricks and SQL Server 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 Databricks, 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 Databricks in real time, and result tables in Databricks sync back into SQL Server, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Databricks 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 Databricks 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.
| Databricks objects | SQL Server objects | |
|---|---|---|
| SQL Warehouses The compute endpoint a sync connects to for query execution. | Stored Procedures T-SQL logic that can validate or post-process synced rows. | |
| Change Data Feed Row-level change records on Delta tables that drive incremental reads. | Databases Instance-level databases that scope a sync's reads and writes. | |
| Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. | Schemas Namespaces (dbo and custom) used to organize synced tables. | |
| Schemas Group tables and views; syncs typically target a dedicated schema per source system. | Tables The primary sync target; rows map to records in connected systems. | |
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | Views Read-side projections used as outbound sync sources. | |
| Views Curated read-only projections used as sync sources for downstream tools. | Columns Field-level mapping targets with T-SQL types. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–SQL Server connection.
Changes in Databricks or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Databricks or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Databricks or SQL Server record.
Track your Databricks ⇄ SQL Server sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Databricks and SQL Server.
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 Databricks and SQL Server 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 Databricks and SQL Server 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 Databricks and SQL Server: authenticate both systems, choose the objects to sync (such as Databricks's SQL Warehouses and Change Data Feed), map fields visually, and changes propagate both ways in milliseconds — no code required.
Databricks: Unity Catalog imposes a three-level namespace (catalog.schema.table) that governs access across workspaces. SQL Server: Change Tracking is a lower-overhead alternative that records which rows changed, but not intermediate values, so it suits net-change syncs. Stacksync's field mapping accounts for these differences between Databricks and SQL Server without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Databricks and SQL Server records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Databricks and SQL Server connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Databricks–SQL Server integration in-house.
Yes — Stacksync ships production-grade connectors for both Databricks and SQL Server. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Databricks: Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns. On SQL Server: SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 Databricks and SQL Server.