Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Normalization
I disagree with the answer. I believe that normalization is still the key
for an efficient running database. With things like snapshots and
materialized views, reducing sql joins is no longer an issue. And a well
designed datababase supports well designed joins.
But I do agree with your statement that good db design is being ignored. All you have to do is to look at *any* of the flickin ERP databases that are being produced today. They break so many rules it ain't even funny. My guess is that the battle between produce/sell it and design it right is tipped to the sell it side.
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
From: Paul Baumgartel [mailto:treegarden_at_yahoo.com]
Sent: Thursday, July 29, 2004 11:32 AM
To: oracle-l_at_freelists.org
Subject: Normalization
I'd love to hear comments on the following Q&A (by a well-known Oracle "expert"). Do list members think that this view prevails today? Am I correct in believing that the importance of normalization, and the reasons for that importance, are given short shrift by many DB designers?
Q: What are the basic guidelines one should keep in mind while designing a database? Is denormalization always good?
Today, I always introduce redundancy into the model whenever it can eliminate an SQL join, but not always. I make my decision based on two criteria:
1 - The size of the redundant item
2 - The volatility of the item (e.g. how often do I need to duplicate updates)
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlput 'unsubscribe' in the subject line.
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org
![]() |
![]() |