Re: Optimizer using the wrong index

You could consider forcing the index with the following syntx:

select colA,colB,colC
from table_name (index index_name)
where.....

This might remedy your current Production problem however it's a
double-edged sword in that you are permanently  (until you remove it)
over-riding the optimizer, so if the fastest access plan were to change
down the road, you wouldn't use it.  I'd only consider this as a stop-gap
measure until you can determine the underlying issue (hopefully others
will speak to that).

Here's a link to a Sybase whitepaper that discusses forceindex.

    http://www.sybase.com/detail?id=2602#538896

Richard