VoltDB Tables and Procedures on One Diagram

DbSchema connects to VoltDB's in-memory, partitioned cluster over JDBC and diagrams tables, views, and stored procedure signatures together — the structural overview a sub-millisecond transaction platform never draws for you.

See the transaction interface: procedure signatures beside the tables
Run ad hoc SELECT, INSERT, UPDATE, DELETE for debugging
Verify event streams landed with the structure you expect
Document a proprietary deployment your team can browse

available for

ISO-27001 certified

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

Free Download

DbSchema showing VoltDB tables and stored procedure signatures on a diagram

Trusted by teams at

The Data Model Hides
Inside Java Stored Procedures

VoltDB earns its sub-millisecond latency by partitioning data across cores and running transactions as compiled procedures. The cost: what the database actually contains — and which procedure touches what — is documented mostly in Java source files.

DbSchema pulls the schema out into the open: tables, views, and procedure signatures on one diagram anyone on the team can read.

Query, Verify & Document
an In-Memory Cluster

Working tools for the people who operate the pipeline, not just the ones who wrote it.

Run ad hoc SQL against VoltDB from the DbSchema editor

Ad Hoc SQL Beside the Procedures

Production traffic belongs in stored procedures; exploration and one-off fixes don't. Run SELECT, INSERT, UPDATE, and DELETE directly, with procedure status codes visible in the grid.

Browse VoltDB in-memory table data in the data explorer

Audit the Stream, Row by Row

Filter and page through in-memory tables to confirm high-throughput events persist correctly — and compare row counts around Kafka, Hadoop, or JDBC export runs.

Generate HTML documentation for a VoltDB schema

Onboarding Without Reading Java

Export the schema — tables, views, procedure signatures — as interactive HTML, so a new developer learns the transaction interface from a browser, not the source tree.

A Model File for a Database
That Lives in RAM

The cluster holds the data; the DbSchema model file holds the design. Keeping them separate is what makes the design reviewable, comparable, and safe to evolve.

Design the VoltDB schema without a cluster connection

Draft Off-Cluster

Evolve the schema in the model while the production cluster keeps serving transactions.

Keep the VoltDB model under version control

History for the Schema

Version the model with the procedure code, so both halves of a change review together.

Read generated DDL for VoltDB before applying it

Statements, Not Surprises

A model edit becomes DDL you read in full before deciding where it runs.

Compare the model with a running VoltDB cluster

Model vs Cluster

Compare the file against a live deployment and see structural drift as a list, not a hunch.

VoltDB Connection Specifics

The client port is 21212, giving the JDBC URL jdbc:voltdb://localhost:21212. Supply the VoltDB JDBC driver (voltdbclient-*.jar) from the VoltDB distribution package or Maven Central — driver class org.voltdb.jdbc.Driver. Username and password are needed only when security is enabled in the deployment XML.

One node's address is enough for multi-node clusters: the client library discovers the full topology automatically. Driver notes on the VoltDB JDBC driver page.