SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Moving SQL Server 2008 R2 to another Machine


Moving SQL Server 2008 R2 to another Machine

Author
Message
smallmoney
smallmoney
Old Hand
Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)

Group: General Forum Members
Points: 380 Visits: 574
Hi we are planning to move our SQL Server default instance (only instance running) to another machine as an upgrade.

I don't want to lose my SQL logins and Agent jobs and was wondering if it's as simple as detaching and attaching the system databases (like master, msdb, model, tempdb) .

If there are any articles on SQL Server Central, that'll be helpful too. Thanks!


old machine had Windows 2003 R2 Enterprise x86 OS and SQL Server 2008 R2 Enterprise x86

new machine is Windows 2008 R2 x64 and SQL Server 2008 R2 Enterprise x64

Both Intel Xeon platforms
Kudikai
Kudikai
SSC-Enthusiastic
SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)

Group: General Forum Members
Points: 188 Visits: 465
I've had mixed results when it comes to restoring system databases. Lately I've given up on that and used a few other methods to make migrating/consolidating servers easier.

I have used this KB for moving logins (SQL and Domain) between servers and it has worked quite well. I don't need to know the passwords because it uses the password hash to recreate the accounts, and it uses the same login SIDs so there is less account cleanup afterwards.

http://support.microsoft.com/kb/918992

I usually use SSIS to move jobs between servers, although it won't clean up any server-specific calls. I highly recommend going through each job to check for those.
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
you can restore the msdb database but it can quickly become messy.

I would definitely advise against it if you use maintenance plans unless you delete them before the move,

If you use proxies these will need recreating which will mean dropping and recreating jobs.

If SSIS packages are stored in msdb they should use some for of external configuration for the server connections.

If service broker is enabled this will need disabling and re-enabling.

So I would only restore msdb if you have a LOT of SSIS packages which don't need altering for a change in server name.

---------------------------------------------------------------------
smallmoney
smallmoney
Old Hand
Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)

Group: General Forum Members
Points: 380 Visits: 574
george sibbald (6/23/2011)
you can restore the msdb database but it can quickly become messy.

I would definitely advise against it if you use maintenance plans unless you delete them before the move,

If you use proxies these will need recreating which will mean dropping and recreating jobs.

If SSIS packages are stored in msdb they should use some for of external configuration for the server connections.

If service broker is enabled this will need disabling and re-enabling.

So I would only restore msdb if you have a LOT of SSIS packages which don't need altering for a change in server name.


Thanks guys. We don't have any SSIS packages on this server.

I do have maintenance plans.

My main concern is making sure the users and sql agent jobs are moved correctly.

I guess for the sql agent jobs, instead of moving msdb I can just script the jobs correct? thanks
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687

I do have maintenance plans.

My main concern is making sure the users and sql agent jobs are moved correctly.

I guess for the sql agent jobs, instead of moving msdb I can just script the jobs correct? thanks


that would be your best bet. Remember though maintenance plans create jobs, do not script those out and copy over, these are best recreated from scratch I am afraid.

---------------------------------------------------------------------
Welsh Corgi
Welsh Corgi
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10152 Visits: 4894
master.dbo (6/23/2011)
[quote]george sibbald (6/23/2011)


We don't have any SSIS packages on this server.

I do have maintenance plans.

My main concern is making sure the users and sql agent jobs are moved correctly.

I guess for the sql agent jobs, instead of moving msdb I can just script the jobs correct? thanks


You can create scripts for the Maintenance Plans, Jobs, Logins and Users and execute them on the Destination Server.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search