Restore MSDB vs. Script jobs
-
Hi all! Im 'cloning' a production box over an alternative server (witch will be used in emergency situations). Witch is the difference between restoring a full backup of the MSDB in the new enviroment, and the job scripting in the production server and subsequent running in the alternative?
Greetings from Argentina!
-
If you restore, you will hold the history information of your jobs. And in the future you plan to use Master/Target Servers to centralize your jobs, or also use replication, then you should restore the msdb db.
-
If you have restored on the clone machine, remember to update the jobs so they wil not be launched on the "dna"-server ;). (update msdb.dbo.sysjobs set originating_server = *** where originating_server = "dna"-server.)
With restore you also keep the DTS-packages. They should also be checked so they refer to the correct server(s).
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Thanks for your response!
-
Also:
Watch out for security contexts if your jobs directly access a server's file system or other resources external to SQL Server. BCP commands, etc.
Bill Bertovich
Bill Bertovich
bbertovich@interchangeusa.com
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply