Physical Database Layout

Hi,

Unlike the gurus on the list, I'm just a programmer who happens to ensure the DB structure is correct/valid, should hold its ground if an external
(read customer's) DBA goes through it with a microscope. Its not always
possible to have a full time DBA suggesting the layout, and moreover, most of the programmers are expected to 'know' RBDMS anyway!

I was hoping if the gurus here can provide me a list of parameters to be taken into consideration (while doing the database design) to ensure that the phsycial database layout itself is optimized for performance. Or if anyone can just point me in the right direction, it'll help me a lot.

Btw, Oracle has more than 200 initialization parameters, all affecting its working in some or the other way. Do the gurus keep all of them at their finger-tips?

TIA,
Manav.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Manavendra Gupta
  INET: manav_at_zycus.com

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: 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).