| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Normalization
Thursday, July 29, 2004, 11:32:22 AM, Paul Baumgartel (treegarden_at_yahoo.com) wrote:
PB> Today, I always introduce redundancy into the model whenever it can
PB> eliminate an SQL join, but not always.
"whenever" but "not always" is kind of a contradiction in itself.
I recall one performance problem, involving a query to lookup records, that I solved by using a trigger to store a copy of a column into another table, thus eliminating the one join that was in a query. In that one case though, you could easily have argued that the underlying design was flawed, and that the two tables, which were one-to-one, should have been one table. Or at least, the frequently queried columns should all have been together in the same table.
Please don't misconstrue me here. I'm not a fan of denormalization. In one instance though, many years ago, I did use the technique to make some users very, very happy.
Best regards,
Jonathan Gennick --- Brighten the corner where you are http://Gennick.com * 906.387.1698 * mailto:jonathan@gennick.com
Join the Oracle-article list and receive one article on Oracle technologies per month by email. To join, visit http://five.pairlist.net/mailman/listinfo/oracle-article, or send email to Oracle-article-request_at_gennick.com and include the word "subscribe" in either the subject or body.
 |
 |