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


System Database restores vs rebuild


System Database restores vs rebuild

Author
Message
karend211 34657
karend211 34657
SSC-Enthusiastic
SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)

Group: General Forum Members
Points: 142 Visits: 201
Bear in mind, the server you restore to should be exactly the same (version, sp possibly even cu, but I'd not swear to that one) as your old one otherwise it is unlikely to work.


Yes, I was wondering about the CU and if it needed to be the same.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)

Group: General Forum Members
Points: 52127 Visits: 17672
karend211 34657 (4/28/2014)
Why would you need a new server just because sql server won't start??


I am thinking worst case scenario & want to be prepared & have a plan for all avenues. Yes, I'd check the windows event log & sql server error log but honestly, unless there is something in there that gives me something to go on, I would be tempted to not waste too much time. - have I mentioned I'm an "accidental" dba -- .net developer 85% of the time.

Thank you everyone for the replies & links posted, I've found them very informative. I think what i've got from this is to practice practice practice the different methods that may be needed for recovery.

In my experience sql server doesnt just stop starting correctly for no reason. Most likely\common reasons are missing folder (somone deleted tempdb folder) or missing permission to a folder.
In just about all cases the sql server log and windows app log will highlight the problem area, you just need to go fix it!

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)

Group: General Forum Members
Points: 52127 Visits: 17672
andrew gothard (4/28/2014)
Bear in mind, the server you restore to should be exactly the same (version, sp possibly even cu, but I'd not swear to that one) as your old one otherwise it is unlikely to work.

i have seen problems before on systems where this hasnt been adhered to for SPs, CU should also be matched too although these are SP based and one may argue not as critical, i dont subscribe to that theory though. I would always match SP and CU.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
GilaMonster
GilaMonster
SSC Guru
SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)

Group: General Forum Members
Points: 216877 Visits: 46278
karend211 34657 (4/28/2014)
I am thinking worst case scenario & want to be prepared & have a plan for all avenues.


To be honest, short of corrupted/missing OS files, I can't think of much which would require a server rebuild to fix.
Edit: Or boot drive failures (RIP my test server)

The 'Not wasting time' is why I wrote that article on a non-starting SQL Server. It covers the common problems, how to diagnose and options for fixing.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


karend211 34657
karend211 34657
SSC-Enthusiastic
SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)SSC-Enthusiastic (142 reputation)

Group: General Forum Members
Points: 142 Visits: 201
The 'Not wasting time' is why I wrote that article on a non-starting SQL Server. It covers the common problems, how to diagnose and options for fixing.


Yes, I read it, book marked it, will keep it & use it in the event I should need it. It's a great resource, thank you for posting it.
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