Skip to content
Data warehouse ⇄ Database

Azure Synapse Analytics to TiDB integration — real-time, two-way sync

Keep Azure Synapse Analytics 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 Azure Synapse Analytics and TiDB

Connect TiDB and Azure Synapse Analytics 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 Azure Synapse Analytics, 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 Azure Synapse Analytics in real time, and result tables in Azure Synapse Analytics sync back into TiDB, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Load CRM and ERP records into Synapse dedicated SQL pool tables for enterprise reporting.
  • 02 Publish warehouse aggregates (account health scores, LTV) from Synapse back into operational tools like a CRM.
  • 03 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
  • 04 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics

Common sync patterns

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in Azure Synapse Analytics and keep TiDB focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from TiDB land in Azure Synapse Analytics as they change, replacing hand-built CDC and batch extract jobs.

What you can sync between Azure Synapse Analytics 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.

Azure Synapse Analytics objects TiDB objects How this pairing syncs
Views Curated projections used when downstream tools should not read base tables directly. Views Logical views for shaping reads before syncing outward. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. Databases MySQL-style schemas addressed by any MySQL-compatible client. External tables is specific to Azure Synapse Analytics and Databases to TiDB — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Schemas is specific to Azure Synapse Analytics and Tables to TiDB — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. Columns MySQL-compatible types mapped to fields in the paired system. Materialized views is specific to Azure Synapse Analytics and Columns to TiDB — each maps to any object or custom field on the other side.
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. Indexes Secondary indexes that keep incremental sync queries efficient. SQL pools is specific to Azure Synapse Analytics and Indexes to TiDB — each maps to any object or custom field on the other side.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. Sequences Server-side ID generation relevant when external systems write rows. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Sequences to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics 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.

Azure Synapse Analytics TiDB Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

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

TiDB Azure Synapse Analytics 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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Azure Synapse Analytics ⇄ TiDB

Connect Azure Synapse Analytics and TiDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–TiDB connection.

Real-time

Two-way sync

Changes in Azure Synapse Analytics or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Synapse Analytics 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 Azure Synapse Analytics or TiDB record.

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and TiDB.

How the Azure Synapse Analytics and TiDB connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

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 Azure Synapse Analytics 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.

  1. 01

    Connect your apps

    Authenticate Azure Synapse Analytics 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Synapse Analytics connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Synapse Analytics ⇄ TiDB
    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
    Azure Synapse Analytics TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Synapse Analytics and TiDB 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
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 464 integrations available for Azure Synapse Analytics and TiDB.

Popular · 7 of 464
Coworkers laughing in front of a laptop in a casual office setting

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