Recover from corrupted .ldf file

[hross2026]

Hello,

Recently, one of our database's mdf and ldf were corrupted. We were able to recover some of the data with the capability of importing and querying the database. However, we were unable to recover ALL of the data. Some of the data is still missing because the tables that data is in contain 'chain mis linkage' errors. We found this error by running a DBCC checkdb/checktable command. DBCC couldn't fix those errors either. We're pretty sure that there is some data still barried under the corruption. Then we thought of the live LDF file. This file should have
recorded every transaction up to the point of failure. So we tried to recover that file, however there are 2 problems. First is that we don't have a back up
of that file and 2nd, that file is also corrupted. I couldn't backup the corrupted ldf file at its current state. It's giving me some unrelated error
message like disk space is out. All I know now is the only hope to recover the missing data is from the LDF file. We tried to use this software from Lumigent Log Explorer to recover it. So far no such luck with that. So
I'm asking anyone who has a similar experience or problem. Please let me know. Any possible way of recovering this LDF file would be great. Where it be from SQL Server's native tools or even if it requires us to invest in some 3rd party software. Any input is helpful. Thank you in advance.
-Heather

 

[SQLBill]

The only way I know of, is to backup the .ldf and then use:

RESTORE LOG dbname
WITH STOPAT <date and time to stop>

But to do that you need the log backup. What do you mean it's corrupted? The error message you did provide indicates you are having a disk (hard drive) problem. So either you don't have enough room to do the backup to disk or your disk is damaged. CHKDSK might work to recover the disk problem (see your system admin for this).

Bottom line is that this might not be a database issue, it might be a hardware problem. If so, that needs fixed before you can try to recover the database. But you just might be totally out of luck if it's a hardware issue and you don't have tape backups.

-SQLBill