Design and Manage Starburst / Trino Databases Visually with DbSchema

DbSchema lets you design, manage, and document Starburst / Trino databases. Create ER diagrams, define tables and columns, and generate SQL scripts - with or without a live database connection.

Use Git to share the design, compare it with the Starburst / Trino database, and deploy changes. DbSchema also includes a data editor, query builder, and HTML5 documentation - everything you need in one tool.

DbSchema Database Designer

Download DbSchema Download Starburst / Trino JDBC Driver

Visualizing Federated Data Across Trino Catalogs

Starburst and Trino federate queries across disparate data sources — Hive metastore, Apache Iceberg tables, JDBC-connected relational databases, and object-store formats — through a unified catalog abstraction. Each catalog exposes its underlying source's schemas and tables through Trino's SQL engine. DbSchema connects to Trino via JDBC and renders catalog-level schemas as ER diagrams, making cross-catalog relationships visible on a single canvas. Data engineers can understand how tables from Hive, Iceberg, and JDBC catalogs relate to each other without manually tracing fully qualified table references in SQL queries.

Build Federated Queries Without Writing SQL

DbSchema's visual query builder supports Trino SQL syntax and lets you join tables from different catalogs without writing fully qualified three-part identifiers. Construct cross-source queries interactively and run them against the Trino coordinator from a desktop client.

DbSchema visual query builder constructing cross-catalog Trino federated queries

Explore Table Data Across Catalogs

The data explorer in DbSchema browses Trino table contents with column filtering and pagination. Engineers can validate catalog contents, inspect Iceberg snapshot data, or sample rows from object-store-backed tables without switching to the Trino CLI or a separate notebook environment.

Browsing Starburst and Trino catalog table data in the DbSchema data explorer

Document the Federated Data Model

DbSchema auto-generates HTML schema documentation from your Trino catalog metadata, producing a shareable reference for the federated data model. Teams use this for data catalog documentation, new hire onboarding, and governance requirements across multi-source analytical environments.

Auto-generated schema documentation for a Starburst/Trino federated data model

Connecting DbSchema to Starburst or Trino

Download the Trino JDBC driver as trino-jdbc-*.jar from trino.io and register it in DbSchema's driver manager. The JDBC URL format for open-source Trino is jdbc:trino://host:8080/catalog/schema. For Starburst Enterprise, use jdbc:trino://host:8080 and specify the catalog and schema in DbSchema's connection UI. Both Kerberos and LDAP authentication are supported by passing the appropriate JDBC connection properties in the advanced connection panel.

Why Teams Use DbSchema with Starburst / Trino

  • Visualize multi-catalog schemas from Hive, Iceberg, and JDBC sources in a single diagram
  • Build cross-catalog queries visually without writing fully qualified three-part table names
  • Document the federated data model for governance and team onboarding
  • Explore table contents across catalogs without switching to the Trino CLI
  • Share schema documentation with consumers of the federated layer