Database Reference
In-Depth Information
Every relational database must be designed to meet data quality, perform-
ance, and scalability requirements. For a database to be efficient, the data
it contains must be maintained in a consistent and logical state.
Normalization helps reveal design requirements that remove potential
data manipulation anomalies.
However, strict normalization must often be balanced against special-
ized query needs and must be tested for performance. It may be necessary
to denormalize certain aspects of a database to ensure that queries return
in an acceptable time while still maintaining data integrity. Every design
you work on should include phases to identify normal forms and a phase to
identify denormalization needs. This practice will ensure that you've re-
moved data consistency flaws while preserving the elements of a high-
performance system.
This completes Part I, which has laid the foundation for building an ef-
fective data model. Part II begins with Chapter 5, Requirements Gather-
ing, which launches the overall business process of designing and
deploying a data model.
Search WWH ::
Custom Search