asked on
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 ?
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 1 Comment.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.