Distribution keys, visible at a glance

DbSchema for Greenplum Distribution-Aware Schema Design

Greenplum spreads your data across segment hosts by distribution key and partition policy. DbSchema connects to the master node, reads that metadata from the catalog, and turns the massively parallel warehouse into an ER diagram data engineers can actually review.

  • Review distribution keys without querying catalog tables
  • Generate DDL with DISTRIBUTED BY and PARTITION BY clauses
  • Run analytical SQL from a desktop editor
  • Compare environments to expose configuration drift
Free Community Edition No signup required 15-day Architect trial included
Free Download

Trusted by teams at

Query Speed Follows the Distribution Key
Catalog Views Keep It Buried

How rows spread across segment hosts is the difference between a parallel scan and a lopsided one — yet distribution and partition choices stay invisible in standard database management tools, reachable only through catalog queries.

DbSchema reads that metadata from the system catalog and shows it on the diagram, so missing partition definitions and questionable key assignments surface before they cost a query plan.

Model, Query & Deploy
the Warehouse Through the Master Node

Everything a Greenplum data engineer touches, reachable from one desktop tool.

Reverse engineer a Greenplum schema with distribution metadata
Distribution Metadata on the Diagram

Connect to the master and DbSchema reflects the full schema — tables, dependencies, distribution keys, and partition policies read from the Greenplum catalog.

Run analytical SQL on a Greenplum cluster from DbSchema
Analytical SQL, Desktop Comfort

Write queries in Greenplum's PostgreSQL dialect with syntax support, result tabulation, and query history; the master dispatches them across segment hosts in parallel.

Preview Greenplum DDL with DISTRIBUTED BY clauses before running it
DISTRIBUTED BY, Reviewed First

Create tables and manage partitions in the visual editor; DbSchema generates the matching DDL, distribution clauses included, ready for the master node.

The Warehouse Schema
Belongs in the Repository

DbSchema stores the Greenplum design as a model file, so schema work follows the same path as code: branch, diff, review, merge. From the approved model, generate the DDL and walk it through staging before the production master sees it.

Greenplum schema synchronization between the Git model and cluster environments

Connecting to the Greenplum Master

A Greenplum cluster is reached like any PostgreSQL-compatible database, aimed at the master rather than a segment host. DbSchema downloads the PostgreSQL JDBC driver automatically — Greenplum shares PostgreSQL's wire protocol — and connects on port 5432, the same default PostgreSQL uses. The URL takes the shape jdbc:postgresql://master_host:5432/dbname.

Issue DDL and DML against the master only: Greenplum distributes the work across segment hosts by itself, so schema management never touches individual segments. Driver details are on the Greenplum JDBC driver page.

See the Distribution Strategy, Not Just Tables

One download covers the free Community Edition and the 15-day Architect trial.

Teams working with Greenplum often use these engines too. Explore dedicated guides and JDBC setup for each.

Browse all 100+ supported databases