Re: Multiple block sizes

[Wolfgang Breitling]

They are not even lookup tables, just dead weight. These off the shelf ERP 
products are so generic, trying to be everything for everyone, that any 
particular installation uses only a fraction of all the tables. Especially 
when you consider that sine Peoplesoft 8, you create all tables for all 
modules, even those that you didn't buy a license for. Granted, what are a 
few 100 meg in today's mega-gigabyte databases. But something in me abhors 
any waste, be it space or time (i.e. performance). And since I have 
relegated those tables already to their own "TINYTBL" tablespace with 
uniform 2-block extents, it is really no additional work to create it with 
the smalled blocksize possible.

At 03:34 PM 9/25/2003 -0800, you wrote:
Wolfgang,

Well, I do understand the buffer cache usage part, but few hundred megs of
disk space and 20 seconds of backup time savings wouldn't make me to start
experimenting with block sizes like that.
I assume index organized tables would be the best solution if you got huge
amount of tiny lookup tables, but yeah, in packaged app you can't just start
changing physical structure...
Tanel.
Wolfgang Breitling
Centrex Consulting Corporation
http://www.centrexcc.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Wolfgang Breitling
 INET: [EMAIL PROTECTED]
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: [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).