TiDB HTAP Schemas on One Diagram

DbSchema connects to PingCAP's TiDB through the MySQL Connector/J driver — TiDB speaks the MySQL protocol — and turns the schema of your HTAP cluster into ER diagrams, SQL tooling, and documentation, self-hosted or on TiDB Cloud.

Reverse engineer tables, views, and indexes through the MySQL interface
Run OLTP and analytical queries from the same editor tab
Review EXPLAIN ANALYZE plans showing TiKV and TiFlash operators
Use one connection profile format for clusters and TiDB Cloud alike

available for

ISO-27001 certified

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

Free Download

DbSchema diagramming a TiDB distributed database schema

Trusted by teams at

The Cluster Shards Itself
Your Schema Still Needs a Map

TiDB splits storage into regions, keeps TiKV rows and TiFlash columns consistent over Raft, and hides all of it behind a MySQL-compatible endpoint. That transparency is the point — but it means the logical schema is the one thing your team still has to understand, document, and evolve deliberately.

DbSchema works at exactly that layer: the tables, keys, and relationships your applications see, diagrammed and versioned like the code around them.

Diagram, Query & Explain
TiDB Through Its MySQL Interface

Everything rides the MySQL protocol — including your existing habits.

Reverse engineer a TiDB schema over the MySQL protocol

Connect Like MySQL, on Port 4000

The bundled MySQL Connector/J reads the TiDB catalog and produces the full ER diagram — no cluster-specific setup, just the right port.

Write HTAP SQL with hints and EXPLAIN ANALYZE against TiDB

One Editor for OLTP and OLAP

Author MySQL-compatible SQL, add hints like READ_FROM_STORAGE(TIFLASH[...]) for columnar execution, and study EXPLAIN ANALYZE output to see which operators ran where.

Organize TiDB tables into focused diagrams

A Distributed Database That Reads Simply

Region splitting stays invisible, so the diagram reads like a single-node schema — split it into per-domain layouts and color-code the areas each team owns.

Schema Changes That Travel
Like Code, Cluster to Cluster

Keep the TiDB schema as a model file in your repository: branch it with the feature, diff it in the pull request, and apply the reviewed change to development, staging, and production clusters in the order you choose.

Synchronizing a Git-versioned model with TiDB clusters

Read Git Workflow Docs

TiDB Connection Essentials

TiDB is compatible with the MySQL 5.7 and 8.0 protocol and listens on port 4000 — not MySQL's 3306, and the wrong port is the most common first-connection mistake. Select MySQL as the database type; DbSchema ships MySQL Connector/J (com.mysql.cj.jdbc.Driver), so the URL is simply jdbc:mysql://tidb-host:4000/mydb.

For TiDB Cloud, copy the connection string from the console: it carries the cluster hostname, port 4000, and mandatory SSL — append ?useSSL=true&requireSSL=true or set SSL in the connection dialog's advanced settings. The root password is defined at cluster creation; there is no default empty password. Details on the TiDB JDBC driver page.

Map Your TiDB Cluster's Schema

Grab the free installer — Community Edition with a 15-day Architect trial, signup-free.

Download Free

Frequently asked questions

Yes. DbSchema connects to TiDB through the MySQL Connector/J driver, since TiDB speaks the MySQL protocol, and reverse-engineers tables, views, and indexes into a visual diagram.

TiDB listens on port 4000 by default, not MySQL's standard port 3306 — entering the wrong port is the most common connection mistake when setting up TiDB for the first time.

Yes. Copy the connection string from the TiDB Cloud console, which includes the cluster hostname and port 4000, and enable SSL in the DbSchema connection dialog since TiDB Cloud requires it.

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