Site5 - Built For Designers & Developers MENU

Corrupted mdf file in sql 2000

[2 Grey Star Level]

hello: i was given a corrupted mdf file, the server the database (sql 2000) crashed and the only file recovered was this .mdf file. I have tried as many of the options that i can find, and still cannot get this database recovered. downloaded several of the programs that claim to be able to recover mdf files and none work.. This latest gives me the following errorQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0xd8b4c0f2). It occurred during a read of page (0:0) in database ID 0 at offset 0000000000000000 in file ‘C:\DBIO\testy.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

I created a new database (sql 2008 r2) since I do not have sql 2000 anywhere. renamed the mdf file and then renamed the corrupted one to the new name and restarted. This then brings up the db in recovery_pending mode and I cannot get it out of that mode. Tried setting it to emergency mode, no luck. Is there anyway for me to recover this db?

No there were no backups of this database at all, and yes, i completely agree that a backup strategy is needed, but i’m just the lucky recipient of the issue

Answer #1


I am very sorry to hear of the troubles you are having. This does sound like a difficult situation, and I am honestly not sure how to resolve this. As you are using MSSQL, our ability to help with this is limited. I’ve done a little digging, and it appears that setting the database to EMERGENCY mode, then repairing it, has worked for some people in the past. I would strongly recommend backing up the database, even in its current state, before trying anything.

Answers Answered By: jdavey [359 Blue Star Level]

Answer #2

If you have the database at a point where it’s barking about running DBCC CHECKDB, have you given that a shot? Let DBCC put the pieces together if it can. If it can’t, well, you may be out of luck.
If the database was on a server that is [several versions] out of mainstream support (did I get that math right? 2000, 2005, 2008, 2008 R2, 2012) I’d consider this recovery exercise to be directly related to the decision not to upgrade [12-year-old] software. I’d report the database to be irreparable and irrecoverable since you have no backup. This jab is .:[NOT]:. directed at you, but at the decision-makers that allow this situation to happen. There. I’m done ranting now. My apologies to all the gentle readers of This stuff just fires me up. I wish you the best of luck.
Regarding the “recovery software” I’d avoid getting my hopes up.
That will solve your corruption issue surely because it helped me to come out of some corruption situations. You can get more information

Answers Answered By: hayatibinesah [2 Grey Star Level]

Answer this Question

You must be Logged In to post an Answer.

Not a member yet? Sign Up Now »

Money Back Guarantees
Click to verify BBB accreditation and to see a BBB report.