MariaDB: Galera Clusters and ColumnStore Tables, Visualized

MariaDB grew past its MySQL roots: Galera Cluster replication, system-versioned temporal tables, the ColumnStore engine. DbSchema reads MariaDB metadata through the MariaDB driver, so the model reflects the server you actually run — designed, compared, and documented on that basis.

Reverse engineer tables, views, foreign keys, and indexes into diagrams
Span several databases of one server in a single layout
Write queries with schema-aware autocomplete and MariaDB syntax support
Design offline in the model, then synchronize changes to the live server

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema modeling a MariaDB schema as an interactive ER diagram

Trusted by teams at

Compatible with MySQL,
Reduced by MySQL Tools

Point a MySQL-only tool at MariaDB and everything MariaDB-specific flattens away: temporal tables look ordinary, ColumnStore tables lose their meaning, and the cluster behind the connection stays invisible. The parts you chose MariaDB for are the parts a generic tool ignores.

DbSchema connects with MariaDB's own Connector/J and models the server as what it is — the basis for designing, comparing, and documenting the schema you actually run.

Model, Compare & Browse
MariaDB Without Guesswork

Design on the canvas, diff against live servers, and check the data behind it all.

Design MariaDB tables visually on the diagram canvas

New Tables Without Hand-Written DDL

Create tables and change existing ones directly on the diagram canvas, organize domains into separate layouts, and export the views for review.

Compare two MariaDB schemas and generate a migration script

Two Databases, Every Difference Listed

Diff the model against a live server — or one MariaDB database against another — and generate the migration script from exactly the differences you approve.

Browse MariaDB table data in the DbSchema data explorer

Rows Without Writing SELECT

Paginate through table data, filter by column, and follow foreign key links visually — against any node of a Galera Cluster, since each carries the full schema and data.

Schema Changes Reviewed
Like Application Code

The MariaDB model is a file in your repository: branch it, diff it, pull-request it. After approval, DbSchema generates the SQL and carries the reviewed change through development, staging, and production — one deliberate step per environment.

MariaDB schema synchronization between the Git-tracked model and live servers

Read Git Workflow Docs

MariaDB Connection: Driver, Port, and Galera Notes

DbSchema fetches MariaDB Connector/J on first use — a different driver from MySQL's Connector/J. The server listens on port 3306, the default MariaDB shares with MySQL, and the URL reads jdbc:mariadb://host:3306/dbname.

For a Galera Cluster, point the connection at one node's address rather than a load balancer; every node carries an identical schema, so any node shows the whole cluster's structure and data. A remote server accepts the connection once the usual bind-address configuration and per-host user grants are in place. A full walkthrough: connecting MariaDB to DbSchema; driver details: MariaDB JDBC driver page.

Model the MariaDB You Actually Run

Grab the installer: Community Edition free, Architect trial for 15 days, zero signup.

Download Free

Tutorials and guides

Connecting MariaDB to DbSchema

Frequently asked questions

Yes. DbSchema connects to MariaDB over JDBC using the MariaDB Connector/J driver, which it downloads automatically, then reverse-engineers the schema into an interactive ER diagram.

MariaDB listens on port 3306 by default, the same as MySQL, and DbSchema builds the JDBC URL as jdbc:mariadb://host:3306/dbname.

Yes. Point the connection at any single node's IP address instead of a load balancer - every Galera node holds an identical schema, so DbSchema reads the full structure and data from whichever node it connects to.

Teams working with MariaDB often use these engines too. Explore dedicated guides and JDBC setup for each.