Real-time sync
Changes in Tableau or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Tableau 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.
Tableau is a read-only source: Stacksync reads its data in real time and delivers it into TiDB, so TiDB always reflects the current state of Tableau — without exports, scripts, or schedulers.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Tableau is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from TiDB into Tableau usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
Signup, usage, and lifecycle events captured in Tableau sync into TiDB as rows, so applications and internal tools can read behavioral data next to the records they already keep.
Segments, cohorts, or scores computed in Tableau sync back into TiDB, where the services that read from the database act on them at query speed without calling the analytics API.
The users, events, orders, and records stored in TiDB land in Tableau as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
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.
| Tableau objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. | 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 the writable direction. | |
| Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Users is specific to Tableau and Databases to TiDB — each maps to any object or custom field on the other side. | |
| Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Databases and Tables is specific to Tableau and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. | Columns MySQL-compatible types mapped to fields in the paired system. | Extract Refresh Tasks is specific to Tableau and Columns to TiDB — each maps to any object or custom field on the other side. | |
| Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. | Indexes Secondary indexes that keep incremental sync queries efficient. | Fields and Columns is specific to Tableau and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. | Sequences Server-side ID generation relevant when external systems write rows. | Published Data Sources is specific to Tableau and Sequences to TiDB — each maps to any object or custom field on the other side. |
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.
DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.
DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.
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.
DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating TiDB records.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Tableau–TiDB connection.
Changes in Tableau or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Tableau or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Tableau or TiDB record.
Track your Tableau ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Tableau and TiDB.
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.
Authenticate Tableau 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.
Pick the Tableau 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between Tableau and TiDB — Tableau is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
On the Tableau side: Projects, Users, Databases and Tables, Extract Refresh Tasks, plus custom fields where Tableau exposes them. On the TiDB side: Databases, Tables, Views, Columns. Stacksync auto-detects both schemas and converts types between the two systems.
Tableau is a read-only source, so this integration runs one-way: Stacksync reads from Tableau in real time and delivers into TiDB. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for Tableau and TiDB: Where Tableau tracks product events: behavior onto stored records; Where Tableau builds cohorts or scores: results your services can read; Analytics on live operational data, minus the pipeline. Signup, usage, and lifecycle events captured in Tableau sync into TiDB as rows, so applications and internal tools can read behavioral data next to the records they already keep.
Tableau: REST API, Metadata API (GraphQL), and VizQL Data Service. Authentication: Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
Tableau: Webhooks cover a fixed set of workbook, data source, view, and admin events; there is no generic row-changed event, so underlying data changes are detected by re-querying. TiDB: TiDB is MySQL-protocol compatible, so existing MySQL drivers, ORMs, and tools connect without modification. Stacksync's field mapping accounts for these differences between Tableau and TiDB without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 361 integrations available for Tableau and TiDB.