At 14:40 05.06.2003 +0000, you wrote:

>Hi SET,
> if i do "update" operation after some huge deletion , what will
>happen?Is there any difference in updation after huge delete?

Actually, I don't know. But I do know that after huge deletions it may be
wise to do a SELECT COUNT(*) because it then may do garbage collection
which otherwise may be postphoned and left to some innocent person
accidentally triggers it (well, at least it ought to be sensible some time
ago).

Though you still haven't told us anything about the most likely candidate
for your slowdown, Firebird has to keep a record of all versions of records
since the Oldest Active Transaction was started, and if there has been done
lots of changes to a table since that time, then things will slow down.
That's why the gap between the Oldest Active Transaction and Next
Transaction ought to be as low as possible.

Set