One tablespace per partition.
If you're not sure of the final size of the partition,
consider putting each tablespace file
with autoexend ON and specify max filesize (MAXSIZE).
For example: if partition extent size is 10M, the autoextend value could
be 100M to have room for 10 more extents.
In my experience, a separate tablespace per partition is advisable; you
don't get the full benefit of partition management options otherwise.
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2001 3:05 PM
>
> We have a 120 Gig
OTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, April 11, 2001 2:06 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Should each partition have it's own tablespace and datafile?
>
>
> We have a 120 Gig datawarehouse that uses
> more than 100 date-bas
We have a 120 Gig datawarehouse that uses
more than 100 date-based partitions. For financial
and political reasons, we have run out of disk space
to give this database as it continues in it's relentless
growth.
The developers have resigned themselves to purge
out some of the old data and get ri
