Skip to content
Data warehouse ⇄ Database

BigQuery to TiDB integration — real-time, two-way sync

Keep BigQuery 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 BigQuery and TiDB

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

Common use cases

  • Maintain a customer master table in BigQuery joined across CRM, billing, and support sources
  • Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

Serve warehouse results at database speed

Aggregates or model outputs computed in BigQuery sync into TiDB, where whatever reads from that database gets them without querying the warehouse.

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 BigQuery and keep TiDB focused on its operational workload.

What you can sync between BigQuery 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.

BigQuery objects TiDB objects
Projects Connection scope: the service account grants access per project. Databases MySQL-style schemas addressed by any MySQL-compatible client.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC.
Partitioned tables Synced like regular tables; partition columns map to target fields. Views Logical views for shaping reads before syncing outward.
Clustered tables Supported; clustering is transparent to the sync. Columns MySQL-compatible types mapped to fields in the paired system.
Datasets Organizational container — you pick which dataset’s tables to sync. Indexes Secondary indexes that keep incremental sync queries efficient.
What ships with BigQuery ⇄ TiDB

Connect BigQuery and TiDB for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and TiDB.

How the BigQuery and TiDB connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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 BigQuery 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 BigQuery 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
    BigQuery connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery 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 · BigQuery ⇄ 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
    BigQuery TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

BigQuery and TiDB integration FAQ

SECURITY

Security teams love 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.

Learn more about security
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for BigQuery and TiDB.

Popular · 8 of 386
All BigQuery integrations All TiDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own