October 24, 2003 at 12:08 am
Hi
The job I've linked to an alert got stuck.
I manualy stoped the job, now it gets launched on and on.
How can I find out how many times sqlagent will still start this job as a
reaction on alerts that have been raised ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 27, 2003 at 8:00 am
This was removed by the editor as SPAM
November 5, 2003 at 8:41 am
- First Disable the Alert That Launched the job
- Then check the Delay between responses that your Alert is setup with (That may be your problem).
- Then Manually Stop the job and make sure the Alert condition is not met again.
HTH
* Noel
November 5, 2003 at 8:52 am
the delay is 0 because that's what the users want ! I know that can cause problems, but I'm not alowed to alter this to a more reasonable figure.
The reason why I want to know how to how many alerts SQLAgent still has to respond to is that I might be better off stop/start sqlagent. But that is not my default reaction.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 5, 2003 at 9:23 am
even if you know it will be lauchend 10 times for the same alert it won't help running the job over and over.
One solution maybe create a table with the date and time the job runned last and log an entry there if the time difference is acceptable other way do nothing and you won't have to stop the job.
But I thought that the real reason for this thread was that the job got stuck?
HTH
* Noel
November 6, 2003 at 5:13 am
<But I thought that the real reason for this thread was that the job got stuck?>
No, that reason is known (user32.dll cannot be initialized ... related to MS KB-article).
After upgrade to sql7.0sp4 is seems that sqlservers memorymanagement is optimized.
I am just curious if there is a way to know how many times sqlagent will launch the specified job again is such a situation.
Jou will notice that when you overload sqlagent by fireing to much times the same alert and for some reason the jobs take longer dan you'd expect, sqlagent raises an error if it gets more than 2000 events backlog. So it keeps account of this number, but how and where ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply