datamodelingtools.com

explainer · published

Conceptual, logical and physical data models: which tools cover each level

A short refresher on the three model levels, then a table of which data modeling tools say they support each one, from the vendors' own pages.

What are the three levels?

The three levels describe the same data at increasing detail.

  • Conceptual: the business things (customer, order, product) and how they relate. No columns or data types. The audience is people who know the business.
  • Logical: entities with attributes, keys and relationships, still independent of any database product.
  • Physical: tables and columns for a specific database, with exact data types, indexes, constraints and naming rules. This is what gets turned into DDL.

Vendors use slightly different words. Oracle, for example, describes logical, relational, physical and multidimensional models in SQL Developer Data Modeler. The idea is the same.

The same order model at three levelsLeft: conceptual boxes Customer and Order joined by a line labeled places. Middle: logical entities with attributes and keys. Right: physical tables with PostgreSQL data types.CONCEPTUALCustomerOrderplacesLOGICALCustomerPK customer idemail (unique)OrderPK order idFK customer idPHYSICAL (PostgreSQL)customersid integer PKemail varchar(255) UQordersid integer PKcustomer_id integer FK
The same two entities at each level. Diagram drawn for this site.

Do you need all three?

Not always. If you mostly document databases that already exist, physical-only tools like dbdiagram.io, DrawSQL or DBeaver are enough.

You need the upper levels when the model has to outlive a particular database, when business people review it, or when one logical model feeds several physical targets. That’s typical of warehouses and enterprise architecture.

Which tools say they support which level?

The table uses only what each vendor states on the pages we read. A “not verified” cell means the page didn’t say, not that the tool can’t do it.

From each vendor's own description, checked Nov 2, 2026. "not verified" = not stated on the pages we read.
toolconceptuallogicalphysicalDDL out
ChartDB nonot verifiedyesyes
dbdiagram.io nonot verifiedyesyes
DBeaver nonot verifiedyesnot verified
DbSchema yesyesyesyes
draw.io (diagrams.net) yesnot verifiednono
drawDB nonot verifiedyesyes
DrawSQL nonot verifiedyesyes
Ellie yesyesyesnot verified
ER/Studio yesyesyesyes
Hackolade Studio not verifiednot verifiednot verifiednot verified
Lucidchart yesnot verifiednot verifiednot verified
Luna Modeler yesyesyesyes
Mermaid (erDiagram) yesyesnono
Moon Modeler not verifiednot verifiedyesyes
MySQL Workbench nonot verifiedyesyes
Navicat Data Modeler yesyesyesyes
Oracle SQL Developer Data Modeler yesyesyesyes
pgModeler nonot verifiedyesyes
QuickDBD nonot verifiedyesyes
Redgate Data Modeler not verifiedyesyesyes
SqlDBM yesyesyesyes
Visual Paradigm yesyesyesyes

Which editions do the levels come in?

Watch for levels sold separately. DbSchema’s purchase page says its Architect edition “adds logical and conceptual design”. Redgate Data Modeler lists “Physical & Logical design” only with its higher-priced tier. Navicat Data Modeler describes converting “a conceptual model to logical, then to physical” in one workspace.

Check the specific edition before buying, not just the product name.

Sources

  1. ER/Studio home page (modeling levels, DDL generation) vendor product page · full page read
  2. Oracle SQL Developer Data Modeler overview vendor product page · full page read
  3. Navicat Data Modeler product page (model conversion) vendor product page · full page read
  4. DbSchema purchase page (editions) vendor pricing page · full page read
  5. Redgate Data Modeler editions vendor pricing page · full page read

Update history

  • Published.

Tools in this guide