Lawrence-136504 (3/18/2010)
Yes. I was manually starting this job so there was no schedule.I created a schedule that runs every 1 minute. This job has one step that has WAITFOR DELAY '00:05:00' so it runs for 5 minutes. I'm now seeing the operator email. 🙂
I'm currently using sysprocesses and sysjobs to capture long running jobs and it has been great but I'm finding that certain sql jobs that use Type: Operating system (CmdExec) and kicks off a console app (workflow), the job hangs and my current process does not capture this issue.
I'm going to add this process and see how it goes. I'll keep you posted in a couple of weeks. Thks!
Oh, good deal! Thanks for bringing that issue to my attention. The intent of this script is to do exactly what you're doing - monitor recurring jobs for problems. When there is not a set schedule, well, I plain did not cover that case :rolleyes:
Please let me know how this works for you - I'll update the code that's posted to do something in the case that there's no schedule set.
Take care:
MJM