August 18, 2011 at 6:54 am
Whilst trying to investigate a SQL Agent job in SSMS I got an error that the job couldn't be found. It seemed strange as the job history was reporting success for the last few days.
What appeared to have happen is the job was renamed in SSMS but the change had not been reflected in the MSDB. I looked around on various forums to see if this had happened to others but I couldn't find any reports on the usual SQL Server blogs I use.
I resolved the issue by guessing that the displayed name in SSMS was out of sync with the MSDB and updating the MSDB value to itself like this.
EXEC dbo.sp_update_job
@job_name = N'My Job Name',
@new_name = N'My Job Name'
I figured the correct job name was being referenced by the job history and the display job name was wrong. My guesses were correct and I can now access the job through the normal SSMS method.
As I didn't find reference to this I thought I'd post this simple solution for anybody who has the same issue in future.
Regards,
GP
August 18, 2011 at 7:07 am
Thanks Gary, I guess you should provide your feedback to Microsoft as well.
Here's the link.
https://connect.microsoft.com/SQLServer/Feedback
M&M
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply