Real-time sync
Changes in MariaDB or Tableau instantly reflect in both systems. No stale data, no manual imports.
Keep MariaDB and Tableau 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 MariaDB, so MariaDB 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 MariaDB 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.
Segments, cohorts, or scores computed in Tableau sync back into MariaDB, 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 MariaDB land in Tableau as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
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.
| MariaDB objects | Tableau objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-side projections used as outbound sync sources. | Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction. | |
| JSON Columns Semi-structured payloads validated with JSON functions. | Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. | JSON Columns is specific to MariaDB and Projects to Tableau — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MariaDB and Users to Tableau — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. | Databases (Schemas) is specific to MariaDB and Databases and Tables to Tableau — each maps to any object or custom field on the other side. | |
| Tables The primary sync target; rows map to records in connected systems. | Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. | Tables is specific to MariaDB and Extract Refresh Tasks to Tableau — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. | Columns is specific to MariaDB and Fields and Columns to Tableau — 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.
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
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 MariaDB records.
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 MariaDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Tableau connection.
Changes in MariaDB or Tableau instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MariaDB or Tableau data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single MariaDB or Tableau record.
Track your MariaDB ⇄ Tableau sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MariaDB and Tableau.
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 MariaDB and Tableau 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 MariaDB and Tableau 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 MariaDB and Tableau — 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: Published Data Sources, Workbooks, Views, Projects, plus custom fields where Tableau exposes them. On the MariaDB side: Primary and Unique Keys, System-Versioned Tables, JSON Columns, Stored Procedures. 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 MariaDB. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for MariaDB and Tableau: Where Tableau builds cohorts or scores: results your services can read; Analytics on live operational data, minus the pipeline; One version of each user or account. Segments, cohorts, or scores computed in Tableau sync back into MariaDB, where the services that read from the database act on them at query speed without calling the analytics API.
MariaDB: SQL wire protocol (MySQL-compatible client/server protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host). 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. Stacksync manages authentication, retries, and rate limits on both sides.
Tableau: The VizQL Data Service returns data from published data sources only, and queries respect the data source's row-level security and the signed-in user's permissions. MariaDB: Composite primary keys are not supported (primary key must be a single column). Stacksync's field mapping accounts for these differences between MariaDB and Tableau 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 375 integrations available for MariaDB and Tableau.