>You are just purposing a feature like the SET COVERAGE command but for internal SQL handling by the REQUERY and TABLEUPDATE, don't you ? Maybe you can intergrate the two and let the SET COVERAGE option register all SQL activities (internal and external) like:
>

Registering the time it takes to execute an SQL operation could be helpful, but I can do this myself if I need to by just recording the time before and after the operation.

>- Index use
>- time needed to index matches (optimizable part)
>- time needed to filter (non optimizable part)
>- time needed for subqueries etc

I think this would be better suited as an extension of SYS(3054) than to SET COVERAGE. ShowPlan is already designed to show query optimization information; the data you propose seems to me as a natural extension of that. The coverage logger OTOH, is geared more toward viewing code optimization on the macro level.