March 22, 2004 at 7:21 am
March 22, 2004 at 7:45 am
Do you have any process wich runs them?
Do you have any sp wich uses sp_Start_job?
Check if any other job, runs them, or if you have any alert that executes them.
March 22, 2004 at 8:11 am
nothing else calls these jobs.
March 22, 2004 at 10:25 am
Grasping at straws.
Are the jobs scheduled from a central server?
GaryA
March 22, 2004 at 11:50 am
nope, local.
March 22, 2004 at 12:53 pm
If you cannot find aything as stated above then use Profiler to monitor who or what may be triggering the jobs. I have never had a job execute after disabling myself.
March 22, 2004 at 2:09 pm
just ran a test on the same server, set a job up, disable, but with current schedule. ran profiler, no outside process set it off, it was the sqlagent ???
March 22, 2004 at 2:12 pm
When viewed in EM after refreshing the job list does it show NO in the enabled column?
March 22, 2004 at 7:31 pm
If you look at the job's job history can you see what called it? It should say something like the following...
The job succeeded. The Job was invoked by Schedule 1 (Schedule Name). The last step to run was step 1 (RunRequiredJob).
OR
The job succeeded. The Job was invoked by User UserLogin. The last step to run was step 1 (RunRequiredJob).
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
This 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.
March 23, 2004 at 12:55 am
Even when disabled, one can still start a job manualy !
ifaik the schedules will not launch the job because it is disabled.
If you doubt it, you could still disable all schedules for the jobs you have disabled. (you will need to disable schedules that are connecte to an alert ! because sqlagent will try to launch the job, notifying it is disabled and not running it, each second,until your sqlagent.out-log-dirve is full or the job is enabled or the schedule is disabled)
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
March 23, 2004 at 2:05 am
How are you disabling the jobs? On the off chance that you're using ad hoc direct updates rather than EM or sp_update_job, then SQL Agent's cache is not refreshed, and it would therefore think the jobs are still enabled.
Cheers,
- Mark
March 23, 2004 at 2:50 pm
Both the Job and Schedule have an "Enabled" Flag. If EITHER is TRUE, the Job can run.
March 23, 2004 at 3:16 pm
Acutally no if Job is enabled and schedule is not it will not automatically run, also same vice versa. However even if both are disabled then it has to be initiated by an external process to the job itself (User, another job, code in a page, another server, etc).
March 23, 2004 at 3:36 pm
I'm working on the theory that it is SQL Agent initiating the jobs, based on the statement "Only deleting the schedule stops them".
If the jobs were being initiated by some other means then deleting the schedule wouldn't change things.
I'm thinking it must be SQL Agent, and that somehow SQL Agent is not being notified by sp_sqlagent_notify.
Cheers,
- Mark
March 23, 2004 at 3:44 pm
I agree that is a possibility but I would be curious as to why and if restarting SQL Agent still has the jobs run. If does then has to be something else but the question would be what. Do you have maybe multiple schedules?
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply