Re: Optimal design, large database
3-11m rows, 200+ columns isn't that big assuming adequate hardware. A bit (10-20%) of "air" for future expansion is a common kludge; it needn't cost much space or performance either, if it's done right.
The main disadvantages of data-driven attribute defs (EAV model, eg
http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm) IMO are more complex development and queries, and slower performance.
PB
Subject
Written By
Posted
Re: Optimal design, large database
June 30, 2007 04:34PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.