Re: Old Chestnut: Tablespace Fragmentation

Thanks to everyone for their comments on this. You've convinced me. I'll go away and worry about something else instead now!

• Bill.

At 04:43 27/02/02 -0800, you wrote:

>I know this one has been done to death: use uniform extents to avoid
>fragmentation; multiple extents don't hurt (within limits).
>
>But what if:
>
>Data Warehouse, one big table on a single disk, full table (batch) scan,
>no concurrent transactions on the database (so no contention for the
>disk), no fragmentation at the file system level, initially empty buffer
>cache (startup), read-only operation so DBWR isn't doing anything on this
>disk. Basically I want to read one data file from end to end. Surely it
>would make sense to have the disk read moving smoothly from one end of the
>disk to the other rather than bouncing about all over the place as it may
>do with multiple extents "randomly" allocated.
>
>Any thoughts?
>
>Thanks
>- Bill.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Bill Buchan
  INET: wbuchan_at_uk.intasys.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).