|
 |
 |
 |
 |
 |
DATABASE
OVER-NORMALIZATION ARTICLES
- ARE
YOU GUILTY OF DATABASE OVER-NORMALIZATION?
The Darker Side of the Golden
Rules -
Gregory T. Dodson
- Normalizing Is Abnormal
BY JEFF FOWLER- Mar 15, 2002 12:00 PM
- A Layman’s Approach to Relational Database Normalization
by Gavin Powell
- February 14, 2003
http://www.oracledbaexpert.com/oracle/papers/Normalization.htm
- "If tables are over-normalized in any application it will run slower, be more
difficult to document, more complex to work with and
more intricate to code."
- i STRONGLY believe in normalization thats what RDBMS
were designed for - but i believe there is such a thing
as over normalization as well"
- MyMASS - 10 Most Common Database Mistakes
- comp.databases - Balancing Normalization with Performance
- In databases, ACID stands for Atomicity, Consistency, Isolation, and Durability.
- Third Normal Form removed even more data redundancy, but at the cost of simplicity
and performance. In our example above, do we really expect
the City and Street names to change very regularly?
- You also came to appreciate
how indexes work to speed searches. You learned how to
normalize a database and why de-normalization and over-normalization
may be a better solution when retrieval speed is of the
utmost importance
- programmer convenience VERSUS end user convenience
"My earlier posting on this
subject stated that end user convenience _is_ a legitimate
reason for
denormalization. "
"The cost of maintaining and extending a database is
far more closely
related to the design of the data than to programmer
convenience."
|
|
 |
 |
 |
 |
|
|
Clients | Services | Contact