Red Gate forums :: View topic - LRQ alerted and actual query duration time discrepancies
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Monitor 3
SQL Monitor 3 forum

LRQ alerted and actual query duration time discrepancies

Search in SQL Monitor 3 forum
Post new topic   Reply to topic
Jump to:  
Author Message
olafdraeger



Joined: 06 Dec 2013
Posts: 1

PostPosted: Fri Dec 06, 2013 11:41 am    Post subject: LRQ alerted and actual query duration time discrepancies Reply with quote

hi,

we are still relatively new to SQLMon so I'm wondering if I may be missing something about those reported query duration times.
when I have configured a low alert to be raised at 10 seconds query duration, SQLMon does create that alert and sends out the respective email with a query duration time in it. this reported time however has nothing to do with the actual query duration itself. is there a way to see the actual query duration in the alert?

as an example, I ran a query in SSMS which ran for 60+ seconds. the low alert time for LRQ is set to 10 seconds. SQLMon raises the alert as expected and reports:
Query duration: 14.98 sec
the medium alert was configured to be raised at 120 seconds, so as this threshold was not reached, no further alerts where raised.

so the question again is how can I see in SQLMon what the actual query time was?

thanks,
olaf
Back to top
View user's profile Send private message
chriskelly



Joined: 19 Apr 2010
Posts: 330
Location: Cambridge, UK

PostPosted: Mon Dec 09, 2013 11:22 am    Post subject: Reply with quote

SQL Monitor periodically checks for running SQL Processes. This check occurs approximately every 15 seconds as part of the wider polling schedule which has been designed to provide the maximum useful information for the minimum impact.

Also, SQL Monitor has to detect the same process twice in succession before it has a duration for it. So in the case of your example, the query was detected for 14.98 seconds of its duration and raised the Low alert. As the query did not continue through the medium threshold the alert was not updated.

The only way to get a more accurate query time from SQL Monitor is to change the polling configuration so that the checks run more frequently. This is not recommended though as if these checks run too often then they can have a negative impact on the SQL Server instance that you are monitoring.
_________________
Chris Kelly
Technical Support Engineer
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group