May 14, 2012 at 12:20 am
I restored few databases from sql 2000 to sql 2008 R2. All but master db could be restored. I changed the connection to single user mode and tried to restore master db but it generated following error:
"The backup of the system database on the device c:\db-backup\Master.dat cannot be restored because it was created by a different version of the server (8.00.2039) than this server (10.50.1600). (Microsoft.SqlServer.Smo)
Your help will be appreciated.
-Puskal
May 14, 2012 at 1:13 am
You cannot restore master from SQl Server 200 to 2008, many interbnal thibgs changed that affect the master database.
What do you want to keep from the old master db - if it is just logins, passwords etc then I would script them out from the old installation to reload to the new. There are options to do this in Management Studio.
Mike John
May 14, 2012 at 12:50 pm
You should be able to restore the master db to a different db name, if you want to pull data from the old master db directly in the SQL 2008 instance.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
May 14, 2012 at 12:53 pm
ScottPletcher (5/14/2012)
You should be able to restore the master db to a different db name, if you want to pull data from the old master db directly in the SQL 2008 instance.
however updating the system tables is no longer possible. you cant just change the GUID of a user by updating the corresponding table. was a great undocumented feature that went away since it was also very easy to screw things up if you were not very careful.
For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]
Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
Jeff Moden's Cross tab and Pivots Part 1[/url]
Jeff Moden's Cross tab and Pivots Part 2[/url]
May 14, 2012 at 1:02 pm
True. I didn't explicitly mention it, but I meant using standard/approved methods, such as generating the legit commands:
CREATE LOGIN
EXEC sp_addlinkedserver
etc..
With the old master db there, you could get (almost) whatever you needed from the existing master.
You could specify the sid on specific SQL users if you wanted to keep those the same, reducing the need to "re-sync" native SQL users as you restore/attach user dbs.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
May 15, 2012 at 2:38 am
You should also never restore MSDB from an older version of SQL Server. Each new version introduces new things to MSDB, and they will not work as expected if you use an old version of MSDB. Also, using an old version of MSDB will put you outside of Microsoft Support.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 15, 2012 at 3:17 am
Could you share the script for same...
Thanks in advance.
Satish
May 17, 2012 at 6:05 pm
Thanks everyone for your help. I found that we cannot restore the Master db from SQL server 2000 to SQL Server 2008 R2. Therefore I restored other databases except system databases. After that I deleted all the users that came from the previous databases restore and created all the users exactly the same as it was in the SQL 2000. This was because the GUID in the old database was not exactly the same in new 2008 database.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply