One Diagram for SingleStore's Rowstore and Columnstore Tables

DbSchema puts SingleStore's two storage engines on a single diagram — rowstore tables beside columnstore tables — and backs it with SQL tooling for transactional and analytical work alike.

Storage type visible per table, shard and sort keys kept in the model
Run point lookups and analytical scans in side-by-side editor tabs
Diff self-managed clusters against Helios workspaces, review the DDL
Connects through the native SingleStore driver or MySQL Connector/J

available for

ISO-27001 certified

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

Free Download

DbSchema diagramming SingleStore rowstore and columnstore tables together

Trusted by teams at

HTAP Means Two Table Types
Your Schema View Should Show Both

SingleStore mixes rowstore tables tuned for point lookups with columnstore tables tuned for analytical scans — in the same database, often in the same query. Which table uses which storage, and how shard keys spread the data, is exactly what a plain table list hides.

DbSchema renders the schema with storage types in view and shard and sort key definitions captured in the model, so distribution decisions stay visible long after they were made.

Explore, Sync & Query
SingleStore from One Desktop App

From the first workspace connection to reviewed migration DDL.

Reverse engineer a SingleStore database into an ER diagram

The Whole Database, Reverse Engineered

Point DbSchema at a cluster or Helios workspace and every table, view, and relationship arrives as an interactive diagram — rowstore and columnstore rendered together with their storage context.

Run SingleStore SQL for transactional and analytical workloads

Tabs for Both Workloads

Fire a low-latency transactional query in one tab and a heavy aggregation in the next, with autocomplete that knows your tables and results exportable to CSV, Excel, or JSON.

Compare SingleStore schemas across environments

Migration DDL You Read First

Compare schemas between environments — self-managed to Helios included — and generate migration DDL covering storage types, shard keys, and column changes, applied only after you approve it.

The Workspace Is Live
The Model Is Yours

DbSchema keeps your schema as a design model file, separate from any running cluster. That file is what you edit, version, and deploy from — deliberately.

Model Without a Cluster

Design tables and keys before the workspace exists, or offline between environments.

A File Git Understands

Commit the model, branch it, and let schema changes go through pull requests.

Review generated SingleStore DDL before running it

DDL Before Deployment

Every planned change becomes SQL you read before it reaches SingleStore.

Apply one reviewed change across SingleStore environments

Same Change, Every Environment

Walk one reviewed change from development through to the production workspace.

Connecting to SingleStore — Drivers, Port, Helios

SingleStore listens on port 3306 by default and is MySQL-compatible, so DbSchema can download either the native SingleStore JDBC driver — URL form jdbc:singlestore://host:3306/dbname — or MySQL Connector/J with jdbc:mysql://host:3306/dbname.

For SingleStore Helios, paste the workspace endpoint from the SingleStore portal in place of a self-managed host and authenticate with workspace credentials; the workspace group's firewall must allow inbound connections from your IP address first. Driver details are on the SingleStore JDBC driver page.

See Rowstore and Columnstore Side by Side

Download free — the Community Edition and a 15-day Architect trial come together.

Download Free

Frequently asked questions

Yes — SingleStore is MySQL-compatible, so DbSchema can connect using either the native SingleStore JDBC driver or the standard MySQL Connector/J driver on port 3306.

Yes — for SingleStore Helios, paste the workspace endpoint from the SingleStore portal and authenticate with workspace credentials; the workspace group firewall must allow inbound connections from your IP first.

Yes — DbSchema renders rowstore and columnstore tables together on the same ER diagram with storage type context, since SingleStore allows both to coexist in one database.

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