Hi Vlad, you're right: there was a private on delete- trigger with a subselect on a non-indexed table.
This error first was covered by the perfomance issue of the non-swept (very old) transaction. If the tools reports stats for the whole database activity if superclassic is used, then it explains the 200 index- reads for a unique row. Thanks for your help Malte ---In [email protected], <hvlad@...> wrote: 1. Do you have complete execution stats, including fetches, backout\purge\expunge and so on ? 2. Do you run SS or CS ? If SS, you should know that tools such as isql\IBE reports stats for the whole database activity, not isolated by the single statement. 3. Do you have triggers for DELETE on this table ? Regards, Vlad
