If you're stuck in "restoring" process you can bring back a database to online state by executing: RESTORE DATABASE YourDB WITH RECOVERY WITH RECOVERY option is used by default when RESTORE DATABASE/RESTORE LOG commands is executed. This was the minimal solution I've tried to resolve this issue (stuck database in restoring state) and I hope it can be applied to more cases.
I resolved this by adding double quotes around - single quotes wouldn't work giving an "Incorrect syntax near. I was having trouble at first because of the database name which contained special characters. Considering the answers of the forum above (Bhusan's) I tried running in the query editor on the side the following: RESTORE DATABASE "" So, after the restoration, the original database remained with a (Restoring.) next to its name. At first this failed and after fixing the new database's file names it was successfully performed - in any case the issue I'm describing re-occurred even if I got this right from the first time. I tried to restore a backup of the database to a new one with a different name. I had a similar issue with restoring using SQL Management Studio. MyDatabase_log C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MyDatabase_log.LDF MyDatabase C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MyDatabase.mdf
The backup contains both a data and log file: RESTORE FILELISTONLY RESTORE DATABASE is terminating abnormally.Īnd exactly what you want in a catastrophic situation is a restore that won't work. The database cannot be recovered because the log was not restored.
Some people have theorized that it's because there was no log file in the backup, and it needed to be rolled forward using: RESTORE DATABASE MyDatabaseĮxcept that, of course, fails: Msg 4333, Level 16, State 1, Line 1 WITH REPLACE -force restore over specified databaseĪnd now the database is stuck in the restoring state.
I backed up a database: BACKUP DATABASE MyDatabaseĪnd then tried to restore it: RESTORE DATABASE MyDatabase
0 kommentar(er)
