I really appreciate it!
ALthough the search itself is still slow, I am able to control when the search happens now. Big improvement!
For what it's worth, the slowness seems to be while retrieving Query Text when it contains a medium to large amount of text in it. I have conditioned myself to execute a very small query before opening and using the Execution History functionality.
Search found 15 matches
- Thu 22 Sep 2022 15:42
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
- Thu 11 Aug 2022 19:57
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
- Mon 08 Aug 2022 14:17
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Thanks for the update.
Would it be possible to make a simple change in SQL Complete v6.12 to include a "Go" button on the search instead of having it search with each mouse click change. That would allow me to set up the search I want without the penalty of multiple searches (and long waits) while I set the Start date (wait) , then End date (wait) then search text (wait).
Although this does not address the slow searches, it would allow us to use the functionality and only pay for the lethargy once.
Would it be possible to make a simple change in SQL Complete v6.12 to include a "Go" button on the search instead of having it search with each mouse click change. That would allow me to set up the search I want without the penalty of multiple searches (and long waits) while I set the Start date (wait) , then End date (wait) then search text (wait).
Although this does not address the slow searches, it would allow us to use the functionality and only pay for the lethargy once.
- Tue 26 Jul 2022 14:43
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Are we still on track for Q3?
- Thu 28 Apr 2022 14:28
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Ugh! I feel for you, hope everything works out.
- Wed 27 Apr 2022 19:18
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Another gentle nag about the availability of the alpha version. Any ETA?
- Wed 09 Mar 2022 17:17
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Just a gentle nag, checking to see if the alpha version is available yet?
- Mon 14 Feb 2022 20:40
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Alpha would be great! Looking forward to it.
- Mon 07 Feb 2022 15:27
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
I'm checking in to see if anyone has been able to look at this and/or provide an ETA? If the performance issue isn't on your radar at this juncture, I would like to re-enforce that some sort of "Go" or 'Search" button would go a LONG way.
- Wed 05 Jan 2022 15:45
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
I appreciate you looking into this. If nothing else, adding a GO button as opposed to every change I make immediately starting a new search would be wonderful.
- Mon 27 Dec 2021 15:57
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
I will email you the file (Don't see where I can attach one here) and details.
- Thu 23 Dec 2021 18:59
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Sorry to say it's back.
The only thing that has changed here is that I am now on v6.9.28. When I first upgraded, searches were coming back relatively quick. Now it is taking a couple of minutes again.
Any suggestions?
The only thing that has changed here is that I am now on v6.9.28. When I first upgraded, searches were coming back relatively quick. Now it is taking a couple of minutes again.
Any suggestions?
- Mon 08 Nov 2021 17:21
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
- Wed 29 Sep 2021 17:53
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Re: Execution History search is painfully slow
Thanks for your help. I just sent the email
- Thu 23 Sep 2021 14:24
- Forum: dbForge for SQL Server
- Topic: Execution History search is painfully slow
- Replies: 27
- Views: 62644
Execution History search is painfully slow
Searching Execution History for keywords has always been very quick. In the last couple of SQL Complete versions it has degraded to taking 15 or more seconds for a simply search. Searching for "Update" when the date filter is set for today and the total records for the day is 166.
I am using SSMS 18.9.2
Any suggestions?
I am using SSMS 18.9.2
Any suggestions?