Skip to content
BENIBIX Learn

Logical Data Model vs Physical Data Model

People think the logical and physical data models are the same drawing. The logical one lists every field and key. It fits any database. The physical one gives each field an exact type for one real database. It also picks the indexes. If you change the database, only the physical model changes.

Data🧭 Foundations

Logical Data Model

The data plan with every field and key added. It is not tied to any one database.

A logical data model adds detail to the conceptual one. It lists every field for each thing, such as a customer's name and email. It marks the keys that make each record unique and that link records. It still says nothing about which database you use. The same logical model could be built in any database.

Example
The library's Loan now has fields: loan ID, member ID, book ID, date out and date due.
Why it matters
It is the full design you can check before you build. Any database can be built from it.
Full entry
Data🧭 Foundations

Physical Data Model

The data plan for one real database. It has exact column types and indexes.

A physical data model is the plan written for one real database. It turns each field into a column with an exact type, such as INT or VARCHAR(100). It adds indexes, partitions and other choices that make reads fast. You can run it as code to create the tables. A change of database means a new physical model.

Example
The library builds Loan in PostgreSQL. Dates are DATE, IDs are BIGINT, and member ID gets an index.
Why it matters
This is the level that runs. Types, indexes and sizes set the speed and cost of every query.
Full entry

In one line

Logical Data Model
The data plan with every field and key added. It is not tied to any one database.
Physical Data Model
The data plan for one real database. It has exact column types and indexes.