PK on partitioned table
- From: <solbeach@xxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 14 Apr 2004 14:39:07 -0400
I have no experience with partitioning, but plan on gaining
some ASAP. I want to partition a table into 52 pieces.
This table will contain a rolling 52 week summary of data.
Each week a new partition will get created & loaded.
The oldest partition will get dropped.
This table will be range partitioned; 1 week per partition.
From what I've read so far, LOCAL index should provide
better performance (as opposed to a GLOBAL index).
Is this correct?
What is the "best" way to the PK index on this table?
Can/should this index reside in a single tablespace?
What are the trade-offs involved?
Thanks In Advance!
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
