Query timings involving substitution variables incorrect

[Paul]

Toad for Oracle Base Edition (64-bit)
Add-Ons:
25.2.376.6086

Hi

I’ve noticed that query timings in Toad that use substitution variables are incorrect and excessive. It seems to be because when you have substitution vars in your query, it takes a while for Toad to close/free up the pop-up variable dialog and it's including that in the execution timing, it shouldn’t. The query timing should only be the query itself executing.

Simple example:

select * from DUAL where DUMMY = 'X';

select * from DUAL where DUMMY = :MYVAL;

Seems to add about 200 msecs on. When tuning this adds a considerable discrepancy.

Regards

Paul

[JohnDorlon]

Hi Paul,

I see what you mean. There are some things going on code-wise between the start and stop besides the lowest-level command where we tell the Oracle client to run the query. Most of it is either Delphi code or ODAC (our third-party oracle access library). The closing/freeing of the dialog is not part of the timing.

I’m not sure how much of that I’ll be able to chop out, but I’ll see what I can do.

-John

[JohnDorlon]

As a workaround - you’ll get more accurate timings from the “Elapsed time” line of Spool SQL. That actually cuts out a lot of the overhead.

In the next beta, the Editor will show the same timings as Spool SQL.

[Paul]

Excellent, thanks as always John.

Paul