If the indexes don't enforce constraints, drop them until 2.0.
If they do, and you can take the database offline during the sweep,
disable the index, run the sweep, then reenable. If constraint indexes
can't be disabled, then drop the constraint and then add it again
(unless the dependency chain is too long to easily manage).

Rick

-----Original Message-----
From: Leyne, Sean [mailto:Sean@...]
Sent: Thursday, March 10, 2005 3:24 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] endless sweep


Ferda,

> Ann and Alex, thank you for your replies.
> What can be done about low-selective FK indices in this matter?

Firebird v2.0 introduces a new index storage structures (part of ODS
11).

The new storage structures have been specifically to resolve the problem
of low selectivity indices and also introduce new per-segment
selectivity information for multi-part indices to improve the optimizer
index selection.

So, what can you do? Wait for v2.0


Sean



Yahoo! Groups Links