Jobs still run, even when DISABLED
-
How about renaming sp_start_job temporary
and await what's going wrong 
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
-
Mark,
That is why I wanted to know what the job history stated. At least then you would know where to look. Once you know what is starting the job then you can try and track down what to do about it. The Job history is the ONLY place that you can find that information.
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB EngineerThis posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed in this post are my own and may not reflect that of my employer.
-
Gary Johnson, sorry but I don't understand your comments.
I looked at the columns in the sysjobhistory table. I saw no column that appears to indicate how/who starts a job. There is a column for "server". I am assuming that this column means the server on which the job executed.
Do I have the wrong table, etc.?
TIA
GaryA
-
GaryA,
Look in the column "message" for job step 0. It should contain something like:
The Job was invoked by Schedule nn
(if invoked by SQLAgent's schedule)
or
The Job was invoked by User xxxxxxxx
(if invoked by outside influences)
Cheers,
- Mark
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply