Skip to content
Database ⇄ Analytics

MariaDB to Tableau integration — real-time data sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MariaDB and Tableau

Give Tableau the users, events, and records that live in MariaDB in real time, and sync the cohorts and scores Tableau computes back into MariaDB where your applications read them.

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.

Common use cases

  • 01 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 02 Mirror the Projects and Workbooks content hierarchy into an internal catalog so teams discover dashboards from a central index.
  • 03 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
  • 04 Replicate ERP or billing master data into MariaDB databases that power customer-facing applications

Common sync patterns

Where Tableau builds cohorts or scores: results your services can read

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.

Analytics on live operational data, minus the pipeline

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.

One version of each user or account

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.

What you can sync between MariaDB and Tableau

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.

How changes propagate between MariaDB and Tableau

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.

MariaDB Tableau Sub-second propagation

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.

Tableau MariaDB Sub-second propagation

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.

Rate-limit considerations

  • MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with MariaDB ⇄ Tableau

Connect MariaDB and Tableau for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Tableau connection.

Real-time

Real-time sync

Changes in MariaDB or Tableau instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MariaDB or Tableau data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single MariaDB or Tableau record.

Observability

Monitoring

Track your MariaDB ⇄ Tableau sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MariaDB and Tableau.

How the MariaDB and Tableau connectors work

MariaDB

Integration surface
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)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MariaDB setup guide

Tableau

Integration surface
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.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

How to connect MariaDB to Tableau — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MariaDB connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MariaDB ⇄ Tableau
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    MariaDB Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

MariaDB and Tableau integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 375 integrations available for MariaDB and Tableau.

Popular · 8 of 375
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.