RE: Large databases

> There was also a quote, the gist of which (I don't recall it exactly),
was
> something like: No large, fully normalized database can perform worth
> diddly.

This is just silly.

Of course, metrics were provided to support this statement, right?

Will a single table be easier to query than a 3 table join? Yes.

So what?

Will a single table be faster to query than a 3 table join? Yes.

Again, so what? Just because option A is faster than option B, does not mean that the performance of option B is unacceptable.

Why not just put the whole database in one table, and then use code tables to determine which rows to query. I think we've had this discussion before.

Jared

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: 
  INET: Jared.Still_at_radisys.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).