Two-way sync
Changes in Apache Druid or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid 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 Apache Druid, 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 Apache Druid in real time, and result tables in Apache Druid sync back into SQL Server, with schema and type mapping between the two systems handled for you.
Rows from SQL Server land in Apache Druid as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Apache Druid 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.
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.
| Apache Druid objects | SQL Server objects | |
|---|---|---|
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Stored Procedures T-SQL logic that can validate or post-process synced rows. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Databases Instance-level databases that scope a sync's reads and writes. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Schemas Namespaces (dbo and custom) used to organize synced tables. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Tables The primary sync target; rows map to records in connected systems. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Views Read-side projections used as outbound sync sources. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Columns Field-level mapping targets with T-SQL types. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–SQL Server connection.
Changes in Apache Druid or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid 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 Apache Druid or SQL Server record.
Track your Apache Druid ⇄ SQL Server sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid 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 Apache Druid 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 Apache Druid 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 Apache Druid and SQL Server: authenticate both systems, choose the objects to sync (such as Apache Druid's Dimensions and Metrics), map fields visually, and changes propagate both ways in milliseconds — no code required.
Apache Druid: Streaming ingestion from Kafka or Kinesis is managed by supervisors designed to provide exactly-once ingestion semantics. SQL Server: CDC setup requires a one-time script run by a DBA with sysadmin privileges. Stacksync's field mapping accounts for these differences between Apache Druid 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 Apache Druid 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 Apache Druid and SQL Server connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–SQL Server integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and SQL Server. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. 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 Apache Druid and SQL Server.