Harry MacDonald
Member²
PLSD 8.0.0.1480
Pretty minor, in the scope of things, but I activated the option to "Notify end of long running queries" with a 10 second delay just to try it out, and I noticed that the time spent waiting for the user (that would be me) to enter values for run-time parameters is included when calculating the delay. If the query waits for 10 seconds for my input, then executes in 0.1 second, I still get the alert.
If the purpose of the delay is to avoid nuisance alerts for queries where the results are returned quickly, I would suggest that it would be more appropriate to trigger the alert based on actual execution time, as reported with the results.
Just my $0.02 worth,
HMD
Pretty minor, in the scope of things, but I activated the option to "Notify end of long running queries" with a 10 second delay just to try it out, and I noticed that the time spent waiting for the user (that would be me) to enter values for run-time parameters is included when calculating the delay. If the query waits for 10 seconds for my input, then executes in 0.1 second, I still get the alert.
If the purpose of the delay is to avoid nuisance alerts for queries where the results are returned quickly, I would suggest that it would be more appropriate to trigger the alert based on actual execution time, as reported with the results.
Just my $0.02 worth,
HMD
