Real-time
Two-way sync
Changes in Dremio or TiDB instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Database
Dremio to TiDB integration — real-time, two-way sync
Keep Dremio and TiDB 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 Dremio and TiDB
Connect TiDB and Dremio 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 TiDB's rows in Dremio, 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 TiDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in TiDB sync into Dremio in real time, and result tables in Dremio sync back into TiDB, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
- 02 Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
- 03 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
- 04 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
Common sync patterns
Offload heavy reads
Point analytical queries at the synced copy in Dremio and keep TiDB focused on its operational workload.
Operational data in the warehouse, minus the pipeline
Rows from TiDB land in Dremio as they change, replacing hand-built CDC and batch extract jobs.
Serve warehouse results at database speed
Aggregates or model outputs computed in Dremio sync into TiDB, where whatever reads from that database gets them without querying the warehouse.
What you can sync between Dremio and TiDB
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.
| Dremio objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Reflections Materialized accelerations that make repeated extraction queries cheaper. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Reflections is specific to Dremio and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Jobs Query execution records useful for monitoring sync workloads. | Views Logical views for shaping reads before syncing outward. | Jobs is specific to Dremio and Views to TiDB — each maps to any object or custom field on the other side. | |
| Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. | Columns MySQL-compatible types mapped to fields in the paired system. | Sources is specific to Dremio and Columns to TiDB — each maps to any object or custom field on the other side. | |
| Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. | Indexes Secondary indexes that keep incremental sync queries efficient. | Physical datasets is specific to Dremio and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | Sequences Server-side ID generation relevant when external systems write rows. | Virtual datasets (views) is specific to Dremio and Sequences to TiDB — each maps to any object or custom field on the other side. | |
| Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Apache Iceberg tables is specific to Dremio and Databases to TiDB — each maps to any object or custom field on the other side. |
How changes propagate between Dremio and TiDB
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.
Dremio TiDB Interval-based propagation
DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.
DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.
TiDB Dremio Sub-second propagation
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Dremio: Bounded by engine capacity and workload management rather than API rate limits.
- TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Dremio ⇄ TiDB
Connect Dremio and TiDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–TiDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dremio or TiDB 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 Dremio or TiDB record.
Observability
Monitoring
Track your Dremio ⇄ TiDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dremio and TiDB.
How the Dremio and TiDB connectors work
Dremio
- Integration surface
- Arrow Flight SQL, JDBC/ODBC, and a REST API
- Authentication
- Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
- Change detection
- Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
- Capabilities
- read · write
- Rate limits
- Bounded by engine capacity and workload management rather than API rate limits
TiDB
- Integration surface
- MySQL wire protocol (SQL)
- Authentication
- Database credentials (MySQL-compatible username/password)
- Change detection
- Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
- Capabilities
- read · write · CDC
- Rate limits
- Throughput scales with cluster size rather than fixed API quotas
How it works
How to connect Dremio to TiDB — 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.
- 01
Connect your apps
Authenticate Dremio and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dremio
connected
TiDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dremio and TiDB 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.
objects · Dremio ⇄ TiDBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dremio TiDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dremio and TiDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dremio and TiDB: authenticate both systems, choose the objects to sync (such as Dremio's Reflections and Jobs), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Dremio and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dremio: Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Dremio side: Jobs, Sources, Physical datasets, Virtual datasets (views), plus custom fields where Dremio exposes them. On the TiDB side: Views, Columns, Indexes, Sequences. 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 Dremio and TiDB: Offload heavy reads; Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed. Point analytical queries at the synced copy in Dremio and keep TiDB focused on its operational workload.
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
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 359 integrations available for Dremio and TiDB.
Popular · 1 of 359
No integrations match .
