Re: Newbie question: Should a table/index ideally always be in a single extent ?

I am surprised that a discussion is not underway on this thread. About a month ago there were several responses both pros and cons of having one large extent vs. several extents. May be everyone is tired by now.

My experience with 1 Gbytes data and 400Mbytes of indexes, soon to grow to 3 Gbytes because of acquisitions, I had no problem using one large extent and it has worked great !!!

One suggestion:

As you have planned use pctincrease = 0 for tables. USE PCTINCREASE =1 for TABLESPACES. If you do this Oracle SMON process will automatically defragment the space after deletions/inserts etc. and you will have lots of contiguous free space. Do not do this for TOOLS, RBS or SYSTEM tablespaces but only the data and index tablespaces.

The need for the regular degragmenting is less.

>

snip
>
> 2. Set for each table INITIAL and NEXT to the same value, such that big
> sites will see a dynamic extension of the table, its tablespace, and its
> datafile every 4 days and small sites will extend every month.
> PCTINCREASE is 0 for both the table and the tablespace.
>
> 3. Regularly defragment the hard drive so that datafiles are contiguous.
>
> --- Raoul
>
Received on Wed May 13 1998 - 16:30:34 CDT