See NuoDB's Distributed Schema in a Single Diagram

NuoDB runs as peer-to-peer transaction engines and storage managers with no single coordination point. DbSchema connects through the broker with the NuoDB JDBC driver and gives the distributed database one visual schema: diagrams, SQL, and environment diffs.

The broker routes the session; DbSchema draws the whole schema
Browse table data without knowing which storage manager holds it
NuoDB SQL in the editor, STORE IN clauses included
Diff development against production and review the resulting DDL

available for

ISO-27001 certified

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

Free Download

DbSchema showing a NuoDB distributed schema as one ER diagram

Trusted by teams at

Processing Happens Everywhere
Understanding Needs One Place

In NuoDB, transaction engines answer queries while storage managers persist the data, and the peers coordinate directly with each other. The architecture removes the single point of failure — and with it, any single place where the schema is simply visible.

DbSchema restores that place: one broker connection, and the tables, indexes, and relationships of the whole database arrange themselves into a diagram.

Query, Browse & Diff
Through One Broker Session

The cluster handles distribution; you work with the schema.

Run NuoDB SQL with STORE IN clauses in the DbSchema editor

NuoDB SQL, Desktop Comfort

Write and run NuoDB SQL — including STORE IN clauses that direct tables to specific storage managers — with results in a paginated, filterable grid.

Browse NuoDB table data across storage managers in DbSchema

Data Without the Distribution Map

Browse and filter any table's rows; the broker routes each request to the right engines, so the physical data placement never becomes your problem.

Diff NuoDB schemas between development and production

Keep Environments Honest

Diff two NuoDB databases structurally, read the ALTER and CREATE statements DbSchema derives, and apply only the changes you approve.

The Cluster Stays Live
The Design Work Happens in a File

The schema lives in a DbSchema model file as well as in the cluster — edit it offline, keep it in Git, and let no change reach a transaction engine before you have read its SQL.

Design the NuoDB schema without a cluster connection

Design Offline

Sketch schema changes with no cluster connection at all.

A File Git Understands

The model diffs and merges like any other source file.

Review generated NuoDB DDL before it runs

DDL You Approve

Planned changes become statements you read before they run.

Promote NuoDB schema changes through environments

Stage, Then Production

Carry one reviewed change across environments in order.

NuoDB Connection Facts

The driver is not bundled: register nuodbjdbc.jar from your installation — typically $NUODB_HOME/jar/nuodbjdbc.jar — in DbSchema's driver manager. Point the connection at the broker, port 48004 by default, giving jdbc:com.nuodb://host:48004/dbname, with database name and schema entered as separate parameters in the connection dialog.

The broker must be running and the target database already started; the broker then routes the session to an available transaction engine automatically. Setup details are on the NuoDB JDBC driver page.