July 9, 2012 at 4:00 am
Hi.
I've got an SQL Job on an Microsoft SQL Server 2008 R2 (SP1) install.
It was failing and we were getting alerts every couple of hours, so whilst I investigated why it was failing I wanted to disable it.
The alert raised was part of the T-SQL statement using Database mail and the "sp_send_dbMail " statement.
I wanted to disable it so in SSMS I right clicked the job and disabled it.
The job ran as per schedule.
I stopped and restarted the SQL Server Agent and updated the Job cache (as per http://www.sqlservercentral.com/Forums/Topic1063710-146-1.aspx#bm1064492)
The job ran as scheduled.
I deleted the Job.
It ran as scheduled.
I stopped the SQL Server Agent.
It ran as scheuded.
I checked msdb..sysjobsteps for the code in the command column incase it was running under andother job, it wasn't there.
(select command from msdb..sysjobsteps where command like '%Diff Backup%')
I asked every member of staff to check their development machines to see if anyone has restored the MSDB to their machine or run the script that created the Job. No one had.
Going nuts now so any help is appreciated.
Giles
July 9, 2012 at 6:20 am
Turns out one of our consultants had taken a copy of the VM environment for a demonstration but had not considered the jobs that might be running before running it.
At least I learnt about SQL Server Agent caching so not all bad.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply