When I run queries on my editor, there is a lag before the results are displayed on the data grid. I understand that there is time spent on executing the queries itself but that isn’t the case here.
for example,
I type this “select sysdate from dual”
I execute it using “Ctrl+Enter” or “F9”.
I see a popup for a fraction of a second before it disappears.
I see the result in the data grid after ~2 seconds.
Opening a new instance of Toad doesn’t fix this. If I restart my machine, this issue is temporarily fixed before it comes back. I thought I could be running out of memory but when I look at resource monitor, I see I have ample free memory and CPU.
Is this something you can help me with?
Thanks
Support Bundle for Toad for Oracle 12.12.0.39
Bundle: Toad for Oracle Xpert (64-bit), Add-Ons:
Edition: Toad for Oracle Developer Edition
Operating System: Windows 7 (Build 7601)Service Pack 1
Is the result section pinned or does it slide up/down? There is a bit of a delay when it slides, I don't know why. If you keep it pinned, then there is no no delay. The "pin" is here, in the top right of the output section.
I wonder if a background session is timing out. Does it happen if you go to Options -> Oracle -> Transactions and uncheck "execute queries in threads"?
Thanks for replying. The queries and execution times are fast. It is the data grid. For the following scripts, I pressed F5 (run as script) in the editor. The "Processing Script" popup window took a time to disappear but the query was fast. Here is the output:
And just to confirm that it's the grid and not something else, disable the "Show Script Grids" option on the Scripts page in Options and then run a select as script (F5). Do you get the text output quickly?
I don't know if it is the way I run my queries. I usually leave a line between my queries and press Ctrl+Enter to execute it. I am used to this for 12 years now.
This displays the results in the "Data Grid" and takes 5+ seconds.
If instead, I highlight my query and press F5, it is very fast.
F5 and Ctrl+Enter couldn't be more different under the hood. To test your Ctrl+Enter vs. not then use F9. Select your query and F9 and compare to Ctrl+Enter. Both of those follow the same internal execution path and would be an apples to apples comparison just taking the statement detection logic out of the loop.