What is the purpose of Physical Database design?
To translate the logical description of data into the technical specifications for storing and retrieving data.
What is the goal of Physical Database Design?
To create a design for storing data that will provide adequate performance and ensure database integrity, security, and recoverability.
Physical Design Process visualized
What are the regulations and standards that impact physical design decisions?
What is a field?
Smallest unit of application data recognized by system software
What do you have to consider when designing a field?
Different Data Types, Picture
What is a default value?
An assumed value if no explicit value
What is range control?
The allowable value limitations (constraints or validation rules)
What is null value control?
Allowing or prohibiting empty fields
What is referential integrity?
Range control (and null value allowances) for foreign-key to primary-key match-ups
How do you handle missing data?
*Triggers can be used to perform these operations*
What is denormalization?
Transforming normalized relations into non-normalized physical record specifications
What are the benefits of denormalization?
What are the costs of denormalizations, due to data duplication?
What are the common denormalization opportunities?
One-to-one denormalization example
Many-to-Many denorm example
Reference data denorm example
What are some risks associated with denormalization?
What other methods can be used to improve the performance of joins?
What is horizontal partitioning?
Distributing the rows of a logical relation into several seperate tables
What are the three types of horizontal partitioning?
When can you use horizontal partitioning?
Useful for situations where different users need access to diffrent rows