At 07:10 PM 3/7/2001 +0100, Nando Dessena wrote:

>...C has an
>additional index on the first two fields of the primary key plus a bunch
>of other (it is selective enough, but not as the primary key, I'd
>suppose).
>
>It happens that my IB5.6 optimizer scans A in natural order, B using its
>primary key index and C using that additional index instead of the
>primary key index.

One thing you might do is change the order of columns in the additional
index on C, so that the two segments of the primary key aren't first.


Regards,

Ann
www.ibphoenix.com
We have answers.