asked on DB IN RECOVERY STATUS IN SQL2005
Hi,
our db is quite huge, the transaction log before we shutting down the box reached at 140GB in size, so after we restart the services the db went to in recovery mode. I have been waiting for 7 hours and it look recovery stuck at 59% since then.
So I decided to stop this progress by stopping sql services then make the db in suspect mode so that I can set db in emergency status.
But now if I want to bring this server back to online ( attach ) and force sql server to online with new log file, what actually will happens to my 140GB trans log size, are we going to says those uncommitted trans will missing from the db due to this kind of recovery technique ?
our db is quite huge, the transaction log before we shutting down the box reached at 140GB in size, so after we restart the services the db went to in recovery mode. I have been waiting for 7 hours and it look recovery stuck at 59% since then.
So I decided to stop this progress by stopping sql services then make the db in suspect mode so that I can set db in emergency status.
But now if I want to bring this server back to online ( attach ) and force sql server to online with new log file, what actually will happens to my 140GB trans log size, are we going to says those uncommitted trans will missing from the db due to this kind of recovery technique ?
Microsoft SQL Server
Last Comment
Aaron Shilo
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.