Skip to content
Data warehouse ⇄ Database

Exasol to MariaDB integration — real-time, two-way sync

Keep Exasol and MariaDB 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 Exasol and MariaDB

Connect MariaDB and Exasol with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want MariaDB's rows in Exasol, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in MariaDB where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in MariaDB sync into Exasol in real time, and result tables in Exasol sync back into MariaDB, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Keep dimension tables such as customers and products aligned with the systems of record.
  • 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
  • 03 Keep several MariaDB instances aligned with one system of record across environments
  • 04 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records

Common sync patterns

Operational data in the warehouse, minus the pipeline

Rows from MariaDB land in Exasol as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Exasol sync into MariaDB, where whatever reads from that database gets them without querying the warehouse.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

What you can sync between Exasol and MariaDB

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.

Exasol objects MariaDB objects How this pairing syncs
Tables Primary sync target; columnar relational tables written with standard SQL. Tables The primary sync target; rows map to records in connected systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Read-only query surfaces often used as curated sources for reverse ETL. Views Read-side projections used as outbound sync sources. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Schemas Namespaces that group the tables a sync reads from or writes into. JSON Columns Semi-structured payloads validated with JSON functions. Schemas is specific to Exasol and JSON Columns to MariaDB — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Stored Procedures Server-side logic that can post-process synced rows. Virtual schemas is specific to Exasol and Stored Procedures to MariaDB — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. UDF scripts is specific to Exasol and Databases (Schemas) to MariaDB — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Columns Field-level mapping targets with engine-typed values. Users and roles is specific to Exasol and Columns to MariaDB — each maps to any object or custom field on the other side.

How changes propagate between Exasol and MariaDB

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.

Exasol MariaDB Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

DeliveryEach detected change is applied to MariaDB as a row-level write, with types converted between the two schemas.

MariaDB Exasol 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.

DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Exasol ⇄ MariaDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Exasol or MariaDB 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 Exasol or MariaDB record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Exasol and MariaDB connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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
How it works

How to connect Exasol to MariaDB — 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 Exasol and MariaDB 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
    Exasol connected
    MariaDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Exasol and MariaDB 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 · Exasol ⇄ MariaDB
    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
    Exasol MariaDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Exasol and MariaDB 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 1 of 371
All Exasol integrations All MariaDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own