Page 1 of 2

Execution History search is painfully slow

Posted: Thu 23 Sep 2021 14:24
by Sunapee
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?

Re: Execution History search is painfully slow

Posted: Thu 23 Sep 2021 15:11
by alexa
We will investigate this issue and will answer you as soon as possible.

Re: Execution History search is painfully slow

Posted: Wed 29 Sep 2021 07:54
by alexa
Unfortunately, we were not able to reproduce tis issue.

Could you please specify what version of dbForge you are using?

Also, please perform the following:
1. Turn on tracing by selecting 'SQL Complete -> Trace -> Start Tracing' from the main menu.
2. Reproduce the issue and send us the *.log file with the latest date from the folder:

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge SQL Complete\
A video or screenshots would be of help.

You can send the reply straight to our support system at supportATdevartDOTcom.

Re: Execution History search is painfully slow

Posted: Wed 29 Sep 2021 17:53
by Sunapee
Thanks for your help. I just sent the email

Re: Execution History search is painfully slow

Posted: Sat 02 Oct 2021 17:30
by alexa
Thank you for the reply.

We will investigate this issue.

Re: Execution History search is painfully slow

Posted: Mon 08 Nov 2021 17:20
by alexa
We were able to reproduce this issue and will fix it in the next product build.

We will notify you once it's available for downloading.

Re: Execution History search is painfully slow

Posted: Mon 08 Nov 2021 17:21
by Sunapee
YOU ROCK!

Re: Execution History search is painfully slow

Posted: Thu 23 Dec 2021 18:59
by Sunapee
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?

Re: Execution History search is painfully slow

Posted: Fri 24 Dec 2021 16:03
by dzhanhira
Hi there!

To reproduce this case we need to have a database ExecutedQueries.db %appdata%\Devart\dbForge SQL Complete\ExecutedQueries and please explain what and how you was doing with a detailed explanation.

Re: Execution History search is painfully slow

Posted: Mon 27 Dec 2021 15:57
by Sunapee
I will email you the file (Don't see where I can attach one here) and details.

Re: Execution History search is painfully slow

Posted: Wed 29 Dec 2021 09:16
by dzhanhira
Hi there!
Just want to duplicate the information:
we have received your email and now we keep investigate your case and once there is an update, we will inform you.

Re: Execution History search is painfully slow

Posted: Wed 05 Jan 2022 15:45
by Sunapee
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.

Re: Execution History search is painfully slow

Posted: Thu 06 Jan 2022 08:42
by alexa
We will take this into account.

Re: Execution History search is painfully slow

Posted: Mon 07 Feb 2022 15:27
by Sunapee
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.

Re: Execution History search is painfully slow

Posted: Wed 09 Feb 2022 09:47
by dzhanhira
Hi there,

Kindly be informed that improvements are planned for version 7.0 and we can provide you with an alpha version
approximately in a month. The official version will be released approximately in a couple of months. Anyway, if you need an alpha one. just let us know.