DatriseAI-first ETL

Tidb Tableau

AI-first ETL from Tidb into Tableau. Governed entities, incremental sync, typed landing tables.

How Datrise loads Tidb into Tableau

Datrise syncs Tidb's records, events, and configuration objects into Tableau as warehouse tables or a refreshed .hyper extract. Flexible or custom fields land in flattened columns for Tableau fields, and timestamps such as created, updated, and status changes are typed as date/datetime fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind a live connection or extract, so re-runs update only what changed. Date-partitioned facts to keep extract refresh quick. Tableau .hyper extracts snapshot data, so Datrise keeps the source tables incremental and lets you choose live vs extract.

Ideal for visual analytics and dashboards in Tableau.

Endpoints

Tidb: SaaS or API data source for analytics and warehouse sync.

Tableau: Salesforce analytics platform for interactive dashboards and visual exploration.

How Tidb entities map to Tableau

Tidb entityTableau objectNotes
recordstidb_recordsid PK · custom fields → flattened columns for Tableau fields
eventstidb_eventsdate/datetime fields events
configuration objectstidb_configuration_objectsid PK · linked to tidb_records

FAQ

How does Datrise handle Tidb's custom fields in Tableau?

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

How does the Tidb to Tableau sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind a live connection or extract.

Related pipelines

Early access

Connect Tidb to Tableau 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.