Scribd
Upload
71 views

Model

The physical data model represents how the logical data model will be implemented in the database, specifying tables, columns, data types, constraints, keys and relationships. It may differ from the logical model due to denormalization for requirements or physical considerations like the database system being used. The process of creating a physical data model involves converting entities to tables, relationships to foreign keys, and attributes to columns, then modifying it based on physical constraints.

Uploaded by

Deepanshu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
71 views

Model

The physical data model represents how the logical data model will be implemented in the database, specifying tables, columns, data types, constraints, keys and relationships. It may differ from the logical model due to denormalization for requirements or physical considerations like the database system being used. The process of creating a physical data model involves converting entities to tables, relationships to foreign keys, and attributes to columns, then modifying it based on physical constraints.

Uploaded by

Deepanshu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Physical data model

July 12, 2009 by Deepanshu Mehta

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: 

• 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.
• Physical data model will be different for different RDBMS. For example, 
data type for a column may be different between MySQL and SQL Server.

The steps for physical data model design are as follows: 

1. Convert entities into tables.
2. Convert relationships into foreign keys.
3. Convert attributes into columns.
4. Modify the physical data model based on physical constraints / 
requirements.

The figure below is an example of a physical data model. 

Physical Data Model


Comparing the logical data model shown above with the logical data model 
diagram, we see the main differences between the two: 

• Entity names are now table names.
• Attributes are now column names.
• Data type for each column is specified. Data types can be different 
depending on the actual database being used.

Possibly related posts: (automatically generated)

• week7
• What does normalization have to do with SQL Server?
• What is a Database, really? Data Storage for Librarians

You might also like