RE: advice required on partioning

  • From: "Christian Antognini" <Christian.Antognini@xxxxxxxxxxxx>
  • To: <jdunn@xxxxxxxxx>
  • Date: Wed, 26 Jan 2005 15:24:17 +0100

Hi John

>1. Partition the table by the date column

Good for the drops.

>2. Create a local partitioned index using that column

According to your description you don't need it.

>3. Create 2 other indexes on the 2 columns used for select statements.
>Should these be non-partitioned or global partitioned?

To drop partitions local indexes should be better.=20

For queries it's important to know if partition pruning will be used or =
not:
- If it is used (i.e. if you have a restriction on the partition key) =
and you get data from few partitions, go for local indexes.
- If it's not used (i.e. if you have no restriction on the partition =
key) and/or you have to scan a large amount of partitions, this can lead =
to poor performance with local indexes --> global or non partitioned =
indexes are better to speedup large range scans without partition =
pruning.


HTH
Chris
--
//www.freelists.org/webpage/oracle-l

Other related posts: