DbSchema connects to a Databricks SQL Warehouse and draws Unity Catalog — catalogs, schemas, tables — as ER diagrams, then adds point-and-click queries, browsable Delta table data, shareable documentation, and DDL you read before it runs.
Trusted by teams at
A maturing lakehouse spreads over dozens of catalogs and hundreds of schemas, and every team knows only its own corner. The workspace UI shows one object at a time, so cross-schema dependencies live in people's heads.
DbSchema reads Unity Catalog through your SQL Warehouse and lays the whole structure on a canvas — a shared picture for architects planning restructuring work and for analysts finding the right table.
Schema on the canvas, data in the grid, documentation in the browser — all from one desktop app.
Connect to a SQL Warehouse and DbSchema renders catalogs, schemas, and tables as a navigable ER model — structure you would otherwise piece together screen by screen.
Split the model into focused diagrams per catalog or domain, color-code groups, and export the views for architecture discussions.
The visual builder turns table and column picks into Spark SQL and runs it on the warehouse — analysts query without touching a notebook.
Browse Delta table contents, filter by column values, and page through results to audit data quality or verify an ingestion job.
Generate HTML documentation from Unity Catalog metadata — diagrams, table definitions, and column descriptions in one shareable export.
Design changes to Unity Catalog objects on the model, then read the generated statements first — nothing reaches the warehouse unread.
The schema design lives in its own model file — editable offline, tracked in Git, and applied only after you have read the DDL it produces.
Refine the design anywhere; connect to the warehouse only when it is time to apply.
Track the model in Git so reviewers see structural changes as clean diffs.
Each planned change is spelled out as DDL before anything executes.
Move an approved change through each environment on your own schedule.
With the model in Git, the Unity Catalog structure rides along with your pipeline code: branch it, review it, merge it. Once the review passes, DbSchema produces the DDL for the change.
One export builds interactive HTML5 documentation: searchable diagrams, table definitions, and comments that open in any browser. Teammates who need schema context get it without direct Databricks access.
Type what you need in plain English and get the query back; paste an unfamiliar statement and get an explanation. The Assistant reads your design model, so it speaks in your catalogs and tables.
See What the AI Assistant Can Do
Download the Databricks JDBC driver from the Databricks
driver download page and register it in DbSchema's driver manager. The URL takes the form
jdbc:databricks://workspace.azuredatabricks.net:443/default;httpPath=/sql/1.0/warehouses/warehouse_id,
where httpPath identifies your SQL Warehouse. Authenticate with a personal access token or
your workspace's OAuth settings, and set the catalog and schema connection
properties to open a specific namespace.
Download free, no account needed — Community Edition plus a 15-day Architect trial.
Teams working with Databricks often use these engines too. Explore dedicated guides and JDBC setup for each.