February 18, 2011 at 11:44 am
I have a job listed under my SQL Server agent (SQL Server 2008 R2, 64 bit on Windows Server 2008 R2, 64 bit). I right clicked the icon and selected Disable. Enable had been greyed out, after I made the selection, Disable was greyed out and there was a small red, down arrow over the icon for that job. Enable was now no-longer greyed out and was selectable.
After a few days, I noticed the process was still running. Actually I noticed it right after the next time it was supposed to run, but had thought a co-worker was running it manually as she'd said she might. When I asked her about it, she said she hasn't been running it and it has been running every day at the scheduled time.
Is there some other manner in which the process would have been run? Is there something that would keep the Disable command from functioning properly? I have other jobs on the same instance that are disabled in the same way and they aren't running, they're behaving as they should. The job has both T-SQL and SSIS steps.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 18, 2011 at 11:58 am
I've got a vague memory of seeing a thread, maybe here, where this was discussed. I think it turned out that the schedule had to be disabled as well for it not to run. I'm not at a machine with SQL Server on it now so can't check this - and I could be mis-remembering of course
February 18, 2011 at 12:04 pm
mazzz (2/18/2011)
I've got a vague memory of seeing a thread, maybe here, where this was discussed. I think it turned out that the schedule had to be disabled as well for it not to run. I'm not at a machine with SQL Server on it now so can't check this - and I could be mis-remembering of course
And I could understand that, it'd be clunky, but make sense. The problem is that I have 3 other jobs that superficially look the same, but don't run. It is just this one job that runs when it says it is disabled, the others actually are disabled.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 18, 2011 at 12:05 pm
OK, my curiosity got the better of me and I booted my SQL machine.
Tried it with a trivial job and it didn't run at the scheduled time when disabled.
I wish I could remember how I'd got to that thread, it's going to bug me now!
Edit - we posted at the same time
February 18, 2011 at 12:07 pm
February 18, 2011 at 12:14 pm
Not a puzzle. Happens to me all the time in SQL 2005. Looks like they didn't fix it in 2k8. It's a job cache issue.
See my posts here:
February 18, 2011 at 12:16 pm
Brandie Tarvin (2/18/2011)
Not a puzzle. Happens to me all the time in SQL 2005. Looks like they didn't fix it in 2k8. It's a job cache issue.See my posts here:
Awesome, thanks Brandie. Now I know what to check whenever I disable something.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 18, 2011 at 12:18 pm
You're welcome. Glad I could help.
February 18, 2011 at 12:20 pm
mazzz (2/18/2011)
http://www.sqlservercentral.com/Forums/Topic829755-146-1.aspx#bm837097%5B/quote%5D
Thanks to you too mazzz. A similar answer and every bit helps.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 18, 2011 at 12:22 pm
February 18, 2011 at 1:04 pm
Interesting. I was going to posit that it was being called by another job or process.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 18, 2011 at 1:06 pm
Jack Corbett (2/18/2011)
Interesting. I was going to posit that it was being called by another job or process.
That was my first thought too, but I know I didnt set that up and no-one else that has access to the machine set that up either.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
February 21, 2011 at 4:41 am
The way to check that is to see if there's another job with Start_Job and the job_id in the msdb job tables. But if you don't see it anywhere, then it's probably the job cache.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply