Re: Lots of tables in O7

scott_at_chuck.sycraft.com wrote:
> My group is building a critical application. One option is to use many tables
> for lookup info (carriers, types of things, etc.) all data driven. This is
> best for the tools we use. Result would be 60+ tables of which 20 would have
> fewer than 20 rows (lookup stuff). Option two would be to put all of that
> lookup stuff in one table.
 

> Which is better for Oracle? Any actual experience?
 

> The answer so far is "design a good database and normalize". Yea, ok but
> lets get real also. Any reality out there?

Oracle's CASE tool puts all lookup info into a single table when you design your database. This is a good indicator that a single table may be your best bet. (actually, two tables, one which lists the domains, and one for all the values contained under each domain.)

• - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Sean_Stasica_at_stortek.com
• - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -