> In general, be skeptical of doctrinaire statements about needing
> "pure" normalized designs. Instead look into "structured
> denormalization" methods, especially if performance will be an issue.
I'll disagree with that, vehemently even. :)
Build a normalized design, denormalize if you find it necessary.
Any other approach to denormalization is counter productive.
Most performance problems are in the code and poorly designed
SQL statements.
Why complicate your life with denorms that must be coded around?
Jared ( yes, I do have an opinion )
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
