October 11, 2007 at 9:20 am
In SQL 2005 I found a job that was clearly marked as disabled within sysjobs but it still runs at its normal schedule. I have also disabled the schedule but I'm going to wait for its normal runtime to see if it continues to run. The job is an SSIS maintenance package that I did not write. Anyone else see this?
October 11, 2007 at 11:05 am
If the job still runs after disabling the schedule, try stopping and restarting the SQL Server Agent service.
Greg
Greg
October 11, 2007 at 11:43 am
even if a job is disabled you can launch it manualy or using sp_start_job.
That's why I don't want sp_start_job in any application !
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 11, 2007 at 12:20 pm
That's a good point. You should see if another job is starting the disabled job.
Greg
Greg
October 12, 2007 at 6:30 am
Resolved! Turns out it was the SQL Agent - stopped and restarted, and the job stopped running.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply