Your Teradata warehouse, mapped end to end

Teradata Warehouse Diagrams and Documentation

DbSchema reads the Teradata data dictionary over JDBC and turns databases, user schemas, and their relationships into ER diagrams, browsable documentation, and a model your DBA team can version and compare.

  • Pull tables from many databases and user schemas onto one canvas
  • Keep a local schema snapshot to review without a live session
  • Export documentation that satisfies governance and audit requests
  • Compare environments and generate the migration script instead of hand-written ALTERs
Free Community Edition No signup required 15-day Architect trial included
Free Download

Trusted by teams at

Twenty Years of Warehouse Growth,
Zero Current Diagrams

A mature Teradata system spreads across hundreds of databases and user schemas, each owning tables that feed marts, staging layers, and downstream extracts. The data dictionary knows how it all connects — the people who have to change it usually don't.

DbSchema turns that dictionary into a picture: cross-database ER diagrams, offline snapshots, and documentation your governance process can actually cite.

Map, Query & Document
the Teradata Warehouse

Three jobs that normally need three tools, handled from one desktop application.

Reverse engineer Teradata databases and user schemas into an ER diagram
Cross-Database Diagrams from the Dictionary

Reverse engineer tables from multiple Teradata databases and user schemas onto one diagram — staging, marts, and their dependencies become visible instead of implied.

Run Teradata SQL in the DbSchema SQL editor
Teradata SQL Without the Full Client Stack

Send Teradata SQL — analytic functions, SET and MULTISET table DDL — through the JDBC driver, browse result sets, and export data without installing Teradata Tools and Utilities.

Generate HTML documentation for a Teradata warehouse schema
Documentation for the Governance Board

Export the warehouse structure as interactive HTML — table definitions, column types, comments, and diagrams — so data-catalog and audit requests stop landing on the DBA queue.

Warehouse Changes,
Reviewed Before They Run

The design model is a file, so it can sit in Git next to the load jobs that depend on it. Compare the model against a second Teradata environment, read the generated migration script, and retire the tradition of hand-written ALTER statements.

Schema synchronization between a Git-versioned model and Teradata environments

Connecting to Teradata: the Practical Details

Teradata listens on port 1025 by default, and the JDBC URL takes the form jdbc:teradata://host/DATABASE=dbname,DBS_PORT=1025. Get the Teradata JDBC driver from the Teradata Downloads portal (developer.teradata.com) and register it in DbSchema under Connections > Manage Drivers. If your deployment authenticates through LDAP or Kerberos, append the corresponding parameters to the JDBC URL.

For Teradata running on AWS or Azure, connect through the VPC endpoint hostname rather than a public IP. Setup details and the URL reference live on the Teradata JDBC driver page.

Put Your Teradata Warehouse on a Diagram

Free Community Edition, 15-day Architect trial, one installer — no signup.