Comments on: SQL Server Agent – Query To Find Long Running Jobs http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/ Homepage of Steve Novoselac Tue, 16 Mar 2010 18:51:06 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: dba http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160624 dba Fri, 12 Mar 2010 15:59:49 +0000 http://blog.stevienova.com/?p=1354#comment-160624 I got duplicate values, like if I have 4 jobs , it showed 8/9, with different results, like the same job is normal & long running. I got duplicate values, like if I have 4 jobs , it showed 8/9, with different results, like the same job is normal & long running.

]]> By: Steve http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160577 Steve Tue, 26 Jan 2010 18:21:58 +0000 http://blog.stevienova.com/?p=1354#comment-160577 yes, if you are lucky enough to have opsmgr yes, if you are lucky enough to have opsmgr

]]> By: kmescha http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160576 kmescha Tue, 26 Jan 2010 18:07:54 +0000 http://blog.stevienova.com/?p=1354#comment-160576 Couldn't we use a similar script within Ops Manager to only trigger the monitor when the job is x% past avg runtime or some other criteria to make this Ops Manager monitor a bit more useful? Couldn't we use a similar script within Ops Manager to only trigger the monitor when the job is x% past avg runtime or some other criteria to make this Ops Manager monitor a bit more useful?

]]> By: Steve http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160519 Steve Mon, 16 Nov 2009 18:34:11 +0000 http://blog.stevienova.com/?p=1354#comment-160519 you are right, the query I put on the blog just look if it is over 5% at this point. Takes AVG + STD of historical run times, * 5%, you might need to tweak the pct's accordingly. this query would have to run every X min/seconds and alert you are right, the query I put on the blog just look if it is over 5% at this point. Takes AVG + STD of historical run times, * 5%, you might need to tweak the pct's accordingly. this query would have to run every X min/seconds and alert

]]> By: Steve http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160531 Steve Mon, 16 Nov 2009 18:34:11 +0000 http://blog.stevienova.com/?p=1354#comment-160531 you are right, the query I put on the blog just look if it is over 5% at this point. Takes AVG + STD of historical run times, * 5%, you might need to tweak the pct's accordingly. this query would have to run every X min/seconds and alert you are right, the query I put on the blog just look if it is over 5% at this point. Takes AVG + STD of historical run times, * 5%, you might need to tweak the pct's accordingly. this query would have to run every X min/seconds and alert

]]> By: sqlrockstar http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160518 sqlrockstar Mon, 16 Nov 2009 17:59:20 +0000 http://blog.stevienova.com/?p=1354#comment-160518 OK, found out that OpsMgr uses sp_help_jobactivity and does a datediff between the start execution time and the current time on the server. also, by default the monitor will flag jobs that have run for longer than 1 and 2 minutes, which is less than helpful, really.<br><br>i love your idea of checking on the average run time. i could put something into PBM but the return results are limited there. so now i am thinking of some powershell, but i don't think that will do what we want here: you want to be notified as soon as a job has exceeded the average by 10%, correct? OK, found out that OpsMgr uses sp_help_jobactivity and does a datediff between the start execution time and the current time on the server. also, by default the monitor will flag jobs that have run for longer than 1 and 2 minutes, which is less than helpful, really.

i love your idea of checking on the average run time. i could put something into PBM but the return results are limited there. so now i am thinking of some powershell, but i don't think that will do what we want here: you want to be notified as soon as a job has exceeded the average by 10%, correct?

]]> By: sqlrockstar http://blog.stevienova.com/2009/11/13/sql-server-agent-query-to-find-long-running-jobs/comment-page-1/#comment-160530 sqlrockstar Mon, 16 Nov 2009 17:59:20 +0000 http://blog.stevienova.com/?p=1354#comment-160530 OK, found out that OpsMgr uses sp_help_jobactivity and does a datediff between the start execution time and the current time on the server. also, by default the monitor will flag jobs that have run for longer than 1 and 2 minutes, which is less than helpful, really.<br><br>i love your idea of checking on the average run time. i could put something into PBM but the return results are limited there. so now i am thinking of some powershell, but i don't think that will do what we want here: you want to be notified as soon as a job has exceeded the average by 10%, correct? OK, found out that OpsMgr uses sp_help_jobactivity and does a datediff between the start execution time and the current time on the server. also, by default the monitor will flag jobs that have run for longer than 1 and 2 minutes, which is less than helpful, really.

i love your idea of checking on the average run time. i could put something into PBM but the return results are limited there. so now i am thinking of some powershell, but i don't think that will do what we want here: you want to be notified as soon as a job has exceeded the average by 10%, correct?

]]>