At 09:48 PM 17-08-01 +0200, you wrote:

> > Guido,
> > Does this slowness persist? Normally, the first query on a large-ish table will be slow after reactivating an index because it is the first opportunity the engine has to rebuild the index - hence a slow-down is expected.
> >
>
>Unfortunately, the slowness persist. Any idea, what the reason could be ?

Some things to try:

1. Inspect the indexes for the lookup table. It would be interesting to see whether you see the phenomenon of two primary indexes. Probably not. But it has been reported elsewhere.

2. It would also be worth looking at the indexes for the table that has the reactivated index, to see whether there are some anomalies there, e.g. two indexes on the same column. This happens when you add a FK to a column that has an index already.

3. What happens if you open the lookup table first (i.e. before the Keysource table)?

4. Do you have any database constraints on either of those columns, other than the FK?

5. Do you have any ColumnAttributes or other client-side properties on those linking columns?

Sorry, no answers, only questions. :(

Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________