DatriseAI-first ETL

TiDB to Snowflake Integration

AI-first ETL from TiDB into Snowflake. Governed entities, incremental sync, typed landing tables.

How Datrise loads TiDB into Snowflake

Datrise syncs TiDB's tables, rows, schemas, indexes, regions, and TiCDC change events into Snowflake as a typed table per source entity. Flexible or custom fields land in VARIANT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP_TZ.

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

TiDB: MySQL-compatible HTAP database with row and column stores.

Snowflake: Cloud data warehouse with separated compute and storage.

How TiDB entities map to Snowflake

TiDB entitySnowflake objectNotes
tablestidb_tablesid PK · custom fields → VARIANT columns
rowstidb_rowsid PK · linked to tidb_tables
schemastidb_schemasid PK · linked to tidb_tables
indexestidb_indexesid PK · linked to tidb_tables

FAQ

How does Datrise handle TiDB's custom fields in Snowflake?

Flexible values are stored as VARIANT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Snowflake types.

How does the TiDB to Snowflake sync stay up to date?

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

Connect TiDB to Snowflake the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.