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


Database went into Restoring State for unknown reason


Database went into Restoring State for unknown reason

Author
Message
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53934 Visits: 17679
Grant Fritchey (11/7/2013)
GilaMonster (11/6/2013)
Restoring or recovering?

A DB will go restoring if someone runs BACKUP LOG ... WITH NORECOVERY ....


In what might be an epic role reversal, don't you mean RESTORE LOG etc.?


Gail is correct here, BACKUP LOG WITH NORECOVERY is used to take a tail log backup and is also used for role switching in a log shipping configuration.

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

"Ya can't make an omelette without breaking just a few eggs" ;-)
afw
afw
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 15
GilaMonster (11/6/2013)
Can also happen if someone starts a restore and stops the restore part way through (perhaps realising they were restoring over the wrong DB).


Could you tell me what to do in this situation? Is there anyway to recover the victimized database? Did the restore not roll back when they hit cancel?
GilaMonster
GilaMonster
SSC Guru
SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)

Group: General Forum Members
Points: 224076 Visits: 46307
afw (5/14/2015)
GilaMonster (11/6/2013)
Can also happen if someone starts a restore and stops the restore part way through (perhaps realising they were restoring over the wrong DB).


Could you tell me what to do in this situation? Is there anyway to recover the victimized database? Did the restore not roll back when they hit cancel?


Drop the partially restored DB and start the restore from scratch. The DB that got restored over is gone.
Restores can't be run in a transaction and the first thing they do is start overwriting the file on disk

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


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