A physical data model (or database design) is a representation
of a data design which takes into account the facilities and constraints of a
given database management system. In the lifecycle of a project it typically
derives from a logical data model, though it may be reverse-engineered from a
given database implementation. A complete physical data model will include all
the database artifacts required to create relationships between tables or to
achieve performance goals, such as indexes, constraint definitions, linking
tables, partitioned tables or clusters.
of a data design which takes into account the facilities and constraints of a
given database management system. In the lifecycle of a project it typically
derives from a logical data model, though it may be reverse-engineered from a
given database implementation. A complete physical data model will include all
the database artifacts required to create relationships between tables or to
achieve performance goals, such as indexes, constraint definitions, linking
tables, partitioned tables or clusters.
Physical data model
represents how the model will be built in the database. A physical database
model shows all table structures, including column name, column data type,
column constraints, primary key, foreign key, and relationships between tables.
Features of a physical data model include:
represents how the model will be built in the database. A physical database
model shows all table structures, including column name, column data type,
column constraints, primary key, foreign key, and relationships between tables.
Features of a physical data model include:
- Specification all tables and columns.
- Foreign keys are used
to identify relationships between tables. - Denormalization may
occur based on user requirements. - Physical
considerations may cause the physical data model to be quite different
from the logical data model.