September 12, 2011 at 8:08 am
HI, All of these qey's are giving me restore % which is 100% but it is actaully recovering after the restore from the past few days not sure when that will be done and whether or not it will finish?
September 12, 2011 at 8:08 am
Tara-1044200 (9/12/2011)
HI, All of these qey's are giving me restore % which is 100% but it is actaully recovering after the restore from the past few days not sure when that will be done and whether or not it will finish?
I'm a fish out of water here. Going to let Gail toke over form here on out.
September 12, 2011 at 8:09 am
I'm still waiting for the info from the error log that I asked for.
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
September 12, 2011 at 9:56 am
What Edition are you using? What is the output of this query (replacing "DBName" with the name of your database)?
Use master;
Select name As [File Name],
type_desc As [File Type],
state_desc As [File State],
size As [File Size]
From sys.master_files
Where database_id = DB_ID('DBName')
May 31, 2012 at 12:22 pm
Did the restore complete? If it did how long did it take. I am in a similar kinda of situation. The restore says 100% processed but it is still in recovery state. It has been more than 32 hours and it is a 1.5TB database. Any ideas on when this would recover.
May 31, 2012 at 1:26 pm
Waiting for an update please!!!
June 2, 2012 at 6:23 pm
Codezilla-292868 (5/31/2012)
Did the restore complete? If it did how long did it take. I am in a similar kinda of situation. The restore says 100% processed but it is still in recovery state. It has been more than 32 hours and it is a 1.5TB database. Any ideas on when this would recover.
If you are experiencing a similar issue, please post your own thread on it.
June 4, 2012 at 6:51 am
We were finally able to bring back the database back up. There is apparently a bug in sql server, which takes a long time for the database to come back up if there is a large log file. The cummulative fix described in the article below
http://support.microsoft.com/kb/2028436/EN-US actually helped us solve the problem. The database was back up in less than 2 hours.
If you need more details let me know.
Thanks.
June 4, 2012 at 7:44 am
That's not a bug. That's a side effect of an improperly configured database.
June 7, 2012 at 2:57 pm
Robert,
If this is not a bug, why would Microsoft not charge us for the support they had provided us during this outage. And the cummulative fix actually helped with the restore being faster.
Thanks
June 7, 2012 at 3:16 pm
Support agreement?
Long recovery time from lots of VLFs is not a bug. There have been several changes that MS made to try and optimise the recovery, knowing how many DBs have badly mis-configured logs.
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
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply