That's a fairly sweeping statement to make without
any justification - after all, at 2K:
The block header is a much larger percentage
of the block size - so you lose space.
The probability of wasting space from the PCTFREE
setting increases - so you lose space.
The memory overhead due to x$bh is fixed per block,
so you use more memory to hold the same volume
(block size x block count) of data.
Index depth may increase through having fewer
entries per branch block.
Latch activity is likely to increase on range scans
because leaf blocks hold fewer entries - you get
the same effect on tables with clustered data -
and the effectiveness of IOTs will particularly be
reduced.
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
Author of:
Practical Oracle 8i: Building Efficient Databases
Screen saver or Life saver: http://www.ud.com
Use spare CPU to assist in cancer research.
-----Original Message-----
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Date: 02 October 2001 21:56
|If your application allows it, and if the Application
|will not change in the future, then use a 2k block
|size for OLTP database.
|
|If you are not sure on the application needs, then
|stick with 4k to be safe.
|
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jonathan Lewis
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).
