DbSchema for Firebolt: Tables, Indexes, and SQL Together

DbSchema connects through the Firebolt JDBC driver and introspects table schemas together with their sparse, aggregating, and join index definitions — so optimization work starts from a diagram instead of a guess.

See index configurations next to the tables they serve
Time queries in the SQL editor while tuning index design
Keep documentation of every table and index current
Model new schemas offline, create them when an engine runs

available for

ISO-27001 certified

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

Free Download

DbSchema diagramming Firebolt tables and index definitions

Trusted by teams at

On Firebolt, Speed
Is a Schema Decision

Firebolt separates compute engines from databases and reaches sub-second analytics through sparse, aggregating, and join indexes. Which index serves which query pattern is schema knowledge — and it usually lives in one engineer's head, invisible to the rest of the team.

DbSchema introspects tables and index definitions together and puts that knowledge on a diagram everyone reads.

Design, Measure & Document
Firebolt Schemas

Index strategy as a visual practice, not tribal lore.

Design Firebolt table schemas with index annotations in DbSchema

Tables and Indexes, One Design

Model new table schemas with index annotations in the offline model, then create them on the cluster once the design is agreed.

Benchmark Firebolt analytical SQL in the DbSchema SQL editor

Benchmark While You Write

The SQL editor shows execution time per run, so you measure what an aggregating index changes — window functions, array unnesting, and all — without switching tools.

Generate schema documentation for a Firebolt database

Documentation That Tracks the Cluster

Export HTML documentation of tables, columns, and index definitions so analytics engineers work from a current reference instead of asking around.

Schema Work Without
Starting an Engine

The model is a local file: design, review, and document with every engine stopped, and connect only when something should actually change on the cluster.

Design Firebolt schemas offline in the DbSchema model

Model While Engines Sleep

Draft and refine table designs with zero compute running.

Version the Firebolt schema model in Git

Diffs in Pull Requests

The schema file versions in Git with your pipeline code.

Review generated SQL before it reaches Firebolt

Statements Shown Before Sent

Review the generated SQL before an engine executes any of it.

Keep Firebolt databases consistent with the model

Databases Kept in Step

Carry one reviewed design across the databases that share it.

Firebolt Connection Essentials

Fetch the Firebolt JDBC driver JAR (com.firebolt.FireboltDriver) from the Firebolt documentation and register it in the driver manager. The URL takes the form jdbc:firebolt://api.app.firebolt.io/mydb, with your database name in place of mydb; all JDBC traffic runs over HTTPS on port 443. Authenticate with service account credentials — client ID and client secret — or a user email and password.

Where several engines are associated with the database, append ?engine=my_engine to direct queries at a particular one; GCP-hosted databases use the GCP endpoint as the host. More on the Firebolt JDBC driver page.