Microsoft “Atlanta”

I recently evaluated Microsoft codename “Atlanta” and assisted my colleague John Joyner with the writing of an interesting  blog post which is now posted on the System Center Operations Manager Unleashed Blog.  This new product provides cloud-based SQL Server monitoring in the web browser.

To view the blog post, go to here: Microsoft “Atlanta” on System Center Operations Manager Unleashed


SQL Server 2000: Error 14274: Cannot delete a job that originated from an MSX server

I don’t work much with older versions of SQL server, but I came across the following error today when trying to disable a scheduled SQL 2000 job while trying to backup a SharePoint Portal Server 2003 database.

Error 14274: Cannot delete a job that originated from an MSX server

This error message has two possible causes: either

  1. the SQL server is not a standalone server, and this message is appropriate, or
  2. the name of the SQL server has changed since the scheduled job was created.

In my case, the scheduled job had been around for over 6 years, and the server had been renamed about 5 years ago.  The job has continued to run and noone needed to make changes to it.

I looked in the sysjobs table in the msdb database and noticed that in the originating_server field, the old server name was still there.  I updated each of them with the following statement:

UPDATE sysjobs SET originating_server='yourNewServerName'

and all was well.