Page 2 of 2

Re: Execution History search is painfully slow

Posted: Mon 14 Feb 2022 20:40
by Sunapee
Alpha would be great! Looking forward to it.

Re: Execution History search is painfully slow

Posted: Wed 09 Mar 2022 17:17
by Sunapee
Just a gentle nag, checking to see if the alpha version is available yet?

Re: Execution History search is painfully slow

Posted: Mon 14 Mar 2022 18:19
by .jp
Hello,

Thanks for the post.

Unfortunately, the alpha version is not available so far.

Best Regards.

Re: Execution History search is painfully slow

Posted: Wed 27 Apr 2022 19:18
by Sunapee
Another gentle nag about the availability of the alpha version. Any ETA?

Re: Execution History search is painfully slow

Posted: Thu 28 Apr 2022 13:50
by dzhanhira
Hi there,

Sorry for the delay!

Kindly note that due to the russian aggression into Ukraine, it takes more time to respond as far as our main offices are in Ukraine.

Currently, our ETA is the 3rd quarter of 2022.

Best regards from Ukraine,
Devart Support Team

Re: Execution History search is painfully slow

Posted: Thu 28 Apr 2022 14:28
by Sunapee
Ugh! I feel for you, hope everything works out.

Re: Execution History search is painfully slow

Posted: Tue 26 Jul 2022 14:43
by Sunapee
Are we still on track for Q3?

Re: Execution History search is painfully slow

Posted: Tue 02 Aug 2022 08:01
by dzhanhira
Hi,

Kindly be informed that the fixes will be included in releases of the 7 Series of SQL Complete. It means that the changes of algorithms will be released not earlier than SQL Complete v.7.0

Currently, we are working on SQL Complete v6.12 with the support of SQL Server 2022. Previously we released SQL Complete v6.11 with the support of SSMS 19. We are developing SQL Complete in parallel with all these processes.

Unfortunately, we need to inform you that releasing the SQL Complete v7.x will take couple of months more.

Re: Execution History search is painfully slow

Posted: Mon 08 Aug 2022 14:17
by Sunapee
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.

Re: Execution History search is painfully slow

Posted: Wed 10 Aug 2022 11:00
by dzhanhira
Thanks for your reply!

Kindly be informed that after we release 6.12, we will make a build with a button specifically for you and provide it for your use.

At the beginning of autumn, we will give you an alpha 7.0 version, as you wanted, where there will be improvements in this area, plus additionally speeding up the display of the compliment sheet and a bunch of other goodies.

Thanks again for helping us with the development of the product and being free to try the alpha.

Re: Execution History search is painfully slow

Posted: Thu 11 Aug 2022 19:57
by Sunapee
You rock!

Re: Execution History search is painfully slow

Posted: Mon 19 Sep 2022 12:28
by Raudar
Hi there,

Thanks for your patience. Please be informed that we are going to send you the email with the link for separate custom build which includes fix for this issue.

In case you get any other issues feel free to reply back to us.

Best regards,
Devart team

Re: Execution History search is painfully slow

Posted: Thu 22 Sep 2022 15:42
by Sunapee
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.