SQL Server Performance Forum – Threads Archive
Problem Restoring Master to Another Server
We’ve encountered problems restoring a master database to another server. Microsoft documentation indicates this can be done through Management Studio, but we were unsuccessful. However, we were able to set the server in Single User mode and restore the master using sqlcmd. In SQL 2000 all user databases would be marked as "suspect" after restoring master to another server. In 2005 we see the databases (not marked as suspect), but cannot access them because they have yet to be restored. Shouldn’t the databases be marked as "suspect" in 2005 just like in SQL 2000? Also, we are unable to restore the user databases through Management Studio or a Query window. We are running SQL Server 2005 EE – SP1. Are we seeing a bug or is the MS documentation incorrect for recovering master in 2005? Thanks, DaveDid you follow thos to restore,
http://msdn2.microsoft.com/en-us/library/ms175535.aspx if you have identicaly servers, what you can do is stop the SQL Server service, copy all the mdf and ldf and then restart the server. But for this both servers should have same paths.
—————————————-
Contributing Editor, Writer & Forums Moderator
http://www.SQL-Server-Performance.Com Visit my Blog at
http://dineshasanka.spaces.live.com/
That is bit different in SQL 2005 as the filegroup handling as compared to 2000 & 2005 versions, also mention what error you are getting in this case. Ensure master is restored successfully. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
@http://www.askasqlguru.com/ This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
]]>