>After restoring a Backup from our Application the BD stays in some strange state. Nothing could be done with it and the error message is "DB is still restoring (or something like this). Even with SSMS I only could drop DB, create a new one and then restore the backup.
>The strangest thing is that this is happened only on one server and I have no clue where I should look.
>
>Restore is executed from a SP and there are no errors returned from it.
>
>The executed command is:
>
>RESTORE DATABASE @BASE_NAME
> FROM DISK = @FILE_NAME
> WITH FILE = 1,
> MOVE @LOGICAL_NAME TO @TODB,
> NOUNLOAD, REPLACE
>
>where all variables has the right values :-)
>
>SQL Server 2008 on Windows Server 2008 both are 64 bits.
>
>BTW the message is:
>
>The database ...... is marked RESTORING and is in a state that does not allow recovery to be run.
>
>
>TIA
Check RESTORE can be restarted after an error. In addition, you can instruct RESTORE to continue despite errors, and it restores as much data as possible (see the CONTINUE_AFTER_ERROR option). For more information, see Responding to SQL Server Restore Errors Caused by Damaged Backups.
from
http://msdn.microsoft.com/en-us/library/ms186858.aspxBTW, there is going to be published a very interesting blog about backup/restoring with compression on LTD site.
If it's not broken, fix it until it is.
My Blog