Re: Index strategy for huge partitioned table

is your situation like as below.

table A partitioned on the basis of a date field say D1, and there is no index for D1?

If so, do your application using SQL queries on this table with WHERE condition on field D1 frequently? How many partitions you defined on that table on field D1.?

Dereck L. Dietz wrote:
> <vinsharma1808_at_gmail.com> wrote in message
> news:1156284107.854682.224310_at_75g2000cwc.googlegroups.com...
> > Hi, The indexes in the partiitoned tables should be based upon the
> > facts 1. Usability 2. maintenance. It all depends upon the column which
> > is part of the index. For any column which is being indexed and is also
> > the partitioning key, should be indexed as local for better perforance.
> > If that column is not partitioned column better to make index global in
> > that case.
>
> What about the situation here where the table is partitioned by a date field
> yet that field is not only NOT part of the partition key but isn't even
> indexed at all?
Received on Tue Aug 22 2006 - 17:41:58 CDT