TiDB to Spreadsheets Integration
AI-first ETL from TiDB into Spreadsheets. Governed entities, incremental sync, typed landing tables.
How Datrise loads TiDB into Spreadsheets
Datrise syncs TiDB's tables, rows, schemas, indexes, regions, and TiCDC change events into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.
Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.
Ideal for lightweight, shareable reporting for non-technical teams.
Endpoints
TiDB: MySQL-compatible HTAP database with row and column stores.
Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.
How TiDB entities map to Spreadsheets
| TiDB entity | Spreadsheets object | Notes |
|---|---|---|
| tables | tidb_tables | id PK · custom fields → JSON-stringified cells for nested fields |
| rows | tidb_rows | id PK · linked to tidb_tables |
| schemas | tidb_schemas | id PK · linked to tidb_tables |
| indexes | tidb_indexes | id PK · linked to tidb_tables |
FAQ
How does Datrise handle TiDB's custom fields in Spreadsheets?
Flexible values are stored as JSON-stringified cells for nested fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spreadsheets types.
How does the TiDB to Spreadsheets sync stay up to date?
It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.
Related pipelines
More destinations for TiDB
More sources for Spreadsheets
Early access
Connect TiDB to Spreadsheets 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.