Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
mjmummert
Starting Member
4 Posts |
Posted - 2012-08-06 : 16:38:46
|
I am upgrading from SQL 2000 SP3 to SQL 2008 R2 on the same physical server. During this install, I am also going from Server 2003 to 2008 R2.Method of thinking:Take backups of latest data, copy over to SAN, and restore the databases to a Server 2003 test machine. Upgrade this server to SQL 2000 SP4, and perform the in-place upgrade to SQL 2008 R2 SP1. During this time, I plan to start the Server 2008 R2 install on the server.After the server is ready to go, I plan to install a fresh copy of SQL 2008 R2 SP1. I have a major concern with the system databases and user logins. Am I able to migrate these databases over to the new server? With our DR testing, we currently restore the master database along with the application databases to our SQL 2000 DR server and everything comes up fine. What issues are we going to run into with trying to restore the system databases in SQL 2008 R2 to a different instance with the same name?Sorry if this has been posted before. I am unable to find the same information that I am trying to perform. I am pretty new to SQL, so any information is helpful.Any help is appreciated. |
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-08-06 : 16:44:05
|
Are you upgrading a server, or migrating to a new server?-Chad |
|
|
mjmummert
Starting Member
4 Posts |
Posted - 2012-08-06 : 16:45:01
|
I will actually be moving to a new server with the same name and IP address.Thanks, |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-08-06 : 16:51:03
|
Then I don't understand this sentance "and restore to the new server - SQL 2008 R2 after Server 2008 R2 has been installed"You should take backups just in case...but there should be no need to restore anything if all goes well with the upgrades.-Chad |
|
|
mjmummert
Starting Member
4 Posts |
Posted - 2012-08-06 : 17:45:52
|
I will need to perform a fresh install of Server 2008 R2, along with SQL 2008 R2, essentially wiping out everything. What effect does this have on the system databases? Will I have to restore them, or will they be fine if I copy and paste them to the location they are currently in? |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-08-06 : 20:04:25
|
Why don't you upgrade rather than do a fresh install? If you want to do a fresh install, it depends on what you are trying to save...If it is just the user databases, then you don't need to restore the system databases, just restore/attach your user databases. There may be some work you need to do with fixing orphaned users, but that is easy enough to do.-Chad |
|
|
mjmummert
Starting Member
4 Posts |
Posted - 2012-08-06 : 21:08:38
|
We have to do a fresh install since the physical server does not have enough space on the C: drive (12 GB total), and it's not possible to upgrade from Server 2003 x86 to Server 2008 R2. I am thinking about just reattaching the user databases, and scripting the login transfers. I will setup the previous backup and maintenance jobs separately. I also plan to rebuild the indexes and run the DBCC CHECKDB with DATA_PURITY commands after install. Is this recommended? Is there anything else I need to look out for with the master and msdb databases?Is it even possible to migrate the system databases to a new server successfully in SQL 2008? I need to if possible for our DR plans and testing. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-08-08 : 14:13:00
|
Never migrated the system DBs in these types of cases. Yes, you should run DBCC CHECKDB with DATA_PURITY. I think you have all of the bases covered.-Chad |
|
|
|
|
|
|
|