![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 7 of 7 total |
![]() |
Sat, Feb 9 2019 9:18 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Can we have a timer showing the TOTAL elapsed time from pressing F9 or clicking Execute for a piece of SQL to display the result set or finish running if update please. It doesn't have to be mega accurate (or at least not in my view) but useful.
The reason I ask is I'm just stress testing a query - I can count to 7 (not to fast either) before it completes yet EDBManager quotes 0 seconds Roy Lambert |
Tue, Feb 12 2019 2:28 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Roy,
<< The reason I ask is I'm just stress testing a query - I can count to 7 (not to fast either) before it completes yet EDBManager quotes 0 seconds >> What kind of query ? Is it a sensitive result set ? If so, then that's probably the reason - there are some technical issues with providing accurate filtering times apart from the main query (insensitive result sets don't have this issue). Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 13 2019 2:59 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Tim
Yup - it was sensitive Using Roy standard counting for the time persuaded me to go a different way anyway. Roy Lambert |
Mon, Feb 18 2019 11:32 AM | Permanent Link |
Adam Brett Orixa Systems | I would second Roy's request here ... though perhaps it is hard to do really accurately & not really worth the effort.
I pretty regularly run SQL in EDB Manager and see time's which don't match the "real time" a query has taken to run. It happens when there are sub-selects and other complications in the statements. (I think). It would still be great if the "elapsed time" was close to the real / actual value. |
Tue, Feb 19 2019 3:11 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Adam
Fully agree about the problems with supplying a "true" time. I'd be happy with a GetTickCount when Execute or F9 is pressed and another one when the information has been displayed and show the difference. After all that's what users will perceive as the time taken. Roy Lambert |
Tue, Mar 12 2019 5:16 PM | Permanent Link |
Mario Enríquez Open Consult | +1
|
Thu, Mar 14 2019 11:52 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Adam,
I looked into this further, and it's not plain sensitive queries that have this issue. It only occurs if you have sub-selects and/or derived tables in the sensitive query. At any rate, it's something that I'm fixing for the next release today, so it will be in 2.31. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |