January 21, 2014 at 1:49 am
Welsh Corgi (1/21/2014)
So I should turn it off on all backup maintenance plans?
Do you want your databases to go into the RESTORING state after a backup?
The Database would be ok for a while but go into a restoring state.
Well, yes. That's exactly what that option does. Take the backup and then switch database into restoring state and leave it there.
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
January 21, 2014 at 8:58 am
I never set that option.
I'm not sure how that happened.
It is a mastery but all off my backup maintenance plans/jobs for that Database got deleted.
Thank you very much!:-)
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 23, 2014 at 4:30 pm
Lynn Pettis (1/18/2014)
Welsh Corgi (1/18/2014)
Lynn Pettis (1/18/2014)
Welsh Corgi (1/18/2014)
Lynn,I had to drop the database and restore. Basic syntax.
I think the problem was that they did not stop the SQL Server Services before they started the Windows upgrade.
I would bet the farm.
Thanks!
Okay, I understand you really don't want me to help so I will go away.
I just don't understand why you refuse to post the complete RESTORE DATABASE command you used.
If your database is still in RECOVERY mode try this:
RESTORE DATABASE [databasename] WITH RECOVERY;
You are being silly.
The database has been restored
The restore is not the problem.
RESTORE DATABASE DW
FROM DISK = 'D:\Backup\Complete\DW\DW_backup_2014_01_17_153721_7634016.bak'
WITH REPLACE,
RECOVERY,
MOVE 'DW' TO 'D:\MSSQL\Data\DW.mdf',
MOVE 'DW_Horizon' TO 'D:\MSSQL\Data\DW_HorizonObjects1.NDF',
MOVE 'DW_log' TO 'D:\MSSQL\log\DW.ldf'
The restore worked fine.
The database went into a restoring state because the SQL Server Service was not stopped during the OS Upgrade.
Do not assume that I do not want help.
Thank you.
Really? I am being silly? You said your database went back into RESTORING. I asked to see the command you used for the restore and you refused to post it when I first asked.
At this point, I think your database was in RECOVERY mode due to the OS upgrade and reboot.
If you are going to ask for help perhaps you should be more willing to answer peoples questions fully and completely, you may get better responses in return.
The problem was not with the restore.
It was with the Transaction Log Backup.
The Backup of the tail of the log and leave the Database in a restoring state need to be applied.
That resolved the issue.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply