Telephone: (480) 722-1227 Toll Free: (888) 722-1227
  Email - Contact
  Register Login   |   Knowledge Base  >  Knowledge Base Systems  >  MSSQL  >  problems with clonning sql server   |   Friday, September 03, 2010 search:    
problems with clonning sql server
Last Post 02 Dec 2008 11:30 AM by Vigilant CIO. 0 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Vigilant CIOUser is Offline
Basic Member
Basic Member
Posts:353

--
02 Dec 2008 11:30 AM  

If you clone a sql server, any existing jobs, dts  will get clonned with the server, but you will not be able to manage them. this data is contained in the msdb database.

You will get the following error when trying to manage this data;

Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved.

msft article 281642 recommends you rename the server back to the orginal name, export the jobs to scripts and re-import them.

A simpler solution is to run a sql update script to change the orginating server name to the new server.;

UPDATE [msdb].[dbo].[sysjobs]
SET [originating_server]=''
WHERE [originating_server]=''

you can also find other server name references in the msdb database

You are not authorized to post a reply.

Active Forums 4.2
Copyright 2006 - 2010 Vigilant Support   |  Privacy Statement  |  Terms Of Use