• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 300
  • Last Modified:

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 ?
0
motioneye
Asked:
motioneye
1 Solution
 
Aaron ShiloChief Database ArchitectCommented:
hi

if you force sql server to start with a database New TRN log then you will loss your commited and uncommited trn in the log .

any way the way to do this is to use: sp_attach_single_file_db
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now