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 |
|
Eagle_f90
Constraint Violating Yak Guru
424 Posts |
 Posted - 2014-10-06 : 21:03:10
|
| I was trying to restore my production backup to my dev databse but something went wrong with the restore and now the production databse is stuck in "Restoring". I have searched and everything I find tells me how to avoid this but no one tells me how to get it out of "Restoring" state. What do I have to do to get my production DB out of this "Restoring" state?-- If I get used to envying others...Those things about my self I pride will slowly fade away.-Stellvia |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-10-07 : 11:57:43
|
| Try this: RESTORE DATABASE db1 WITH RECOVERYBut you might need to restore your last full backup (plus differential if you do those) and then the transaction log chain.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
Shanky
Yak Posting Veteran
84 Posts |
Posted - 2014-10-07 : 15:59:13
|
| IIRC there was bug in RTM version of SQL Server 2012 that when intellisence was enabled restore operation would terminate I guess that is not your case. So what is SP level of database ?Other thing are you sure your backup was not corrupt. Can you side by side run restore verifyonly on backup just to rule out possibility of corrupt backup(although only successful restore guarantees backup is complete in all format)'Something went wrong' is not a clue you have to tell us by looking in errorlog what actually is problem. if restoring with recovery succeeds it would be clear that you were restoring database with NORECOVERYHope this helpsRegardsShankySQL Server MVPhttp://social.technet.microsoft.com/wiki/contents/articles/24253.list-of-articles-by-shanky.aspx |
|
|
|
sunder.bugatha
Yak Posting Veteran
66 Posts |
Posted - 2014-10-08 : 03:45:28
|
| Check the % of restore in SQL Error log. If the t-log is too large then it will take ample amount of time for the db to recover and come online.Hema Sunder |
|
|
|
|
|
|
SQL 2014 stuck in "Restoring" state