Posted by Gert-Jan Strik on 07/08/05 18:41

An index can be traversed both ascending and descending. This means that
changing the index order (in the index definition) is never useful for
single column indexes.

If you have compound indexes, then the order can influence performance
of some very specific queries. Generally I would not worry about the
index order.

Gert-Jan


Trevor Best wrote:
>
> I have a unique index based on the following columns:
> ProjectID (int)
> MaterialCatalogID (int)
>
> Material catalogues are pretty much static but projects are dynamic and
> people are most likely to be working on the latest project so would
> using a descending sort on the ProjectID in the index gain any
> performance?

[Back to original message]