The tab history feature is great, but has anyone noticed it tends to run a little slow. I'm not sure if it's just me or if an update has caused the slowness.
Comments
6 comments
-
Hi, Thank you for your forum post.
What version of SQL Prompt are you using?
I am not aware of the Tab History feature of SQL Prompt to be a performance problem. However, it has been known that the Code Analysis feature of SQL Prompt to cause performance issues.
If you expand the SQL Prompt menu item in the Toolbar -> By default the Enable Code Analysis option is enabled. If you disable the Enable Code Analysis option, does this improve the performance of the Tab History feature?
Many Thanks
Eddie -
Thanks Eddie. You're right. That did speed it up. I guess I'll put up with the slowness because I like the Code analysis too much.
And I'm on version 9.5.10.10741. -
Hi, Thank you for your reply.
If the performance degrades to a point where this becomes a blocker for you, please submit a support ticket via the support portal https://productsupport.red-gate.com/hc/en-us and click the 'submit a request' blue button.
I guess you can enable the Code Analysis feature when required and disable when you do not need to use it.
Many Thanks
Eddie -
I'm using 10.0.1.12389 and I clocked this at ~6 seconds to open regardless of whether Code Analysis is enabled or not. It has been that way for several versions
-
Agreed with TimB - the 10.0.1.12389 has slowed it down showing things significantly.
-
I'm on 11.0.6.17341 and it is painfully slow (regardless of Code Analysis being enabled). It takes about 20 seconds for the search screen to appear and about 30 seconds for results to appear. Is anyone else encountering that speed drop or is it just me running on Apple Silicon? (via Parallels with Windows 11 Pro v. 21H2 64-bit ARM-based processor)
Back when SQL History ran fast (I think it was Tab History then), the search textbox on the main screen actually allowed you to enter text there rather than acting like a button as it does now. It would be nice if that could happen again.
Just glad that “query” isn't being returned in the search for no apparent reason anymore.
Add comment
Please sign in to leave a comment.