• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 293
  • 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 ShiloCommented:
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

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

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