July 26, 2004 at 3:26 pm
I have a new active/passive SQL2000 cluster server (Enterprise Edition, SP3a) to replace a standalone installation (same OS, same DBMS version). Everything has been moved over OK, except that there are a lot of SQLAgent jobs on the old db server, and I figured that the easiest way to move them over would be to dump and load msdb. However, the msdb database on the new cluster is always in use by the sqlserver cluster processes.
How do I restore the msdb database and not bring down the cluster?
Regards, Melissa
July 26, 2004 at 7:09 pm
You can script the jobs.
How to script jobs using Transact-SQL (Enterprise Manager)
K. Brian Kelley
@kbriankelley
July 26, 2004 at 8:05 pm
Use Cluster administrator to take SQL Server Agent resource offline, rename the original msdb database files (both mdf and ldf), replace them with the files from old server and bring same resource online.
After doing that, you also have to update system table "sysjobs" with new server name.
July 27, 2004 at 3:48 pm
Thank you. Both of these are good suggestions. I had wanted to avoid scripting the jobs because of embedded "go"'s in some of the transact-SQL command windows; these "go"'s cause errors in the scripting process.
Regards, Melissa
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply