Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-11-02 : 09:02:19
|
| Cari writes "We had a multiple head crash on a SQL Server 7 database developed by a contractor. There was no database backup routine in place. There was a network backup (Backup Exec) being taken. The mdb file was reported as "recovered" from the Backup Exec copy, but would not reload in SQL Server 7. In order to return to production status (now with backups), the recovery effort was abandoned and the server rebuilt from scratch.However we know there is a three day period for which transactions were lost.The ldf file was recovered. Viewing the ascii version, we can see evidence of transaction records. But in ascii we can't tell date and time or any numeric field, just text. Since the ldf file is now "orphaned" from the database, we haven't been able to create a back up of it to restore.Also I haven't been able to trick Log Explorer to see it since it is not part of the database. Although we have worked with other databases (mostly db2) we are new to SQL server, so this has been extra frustrating.I don't have to restore this log... just see date and time with the transaction values. We will happily reenter the data if we can identify it.Is there any hope?Thanks." |
|
|
|
|
|
How can I read the ldf log when the database has been destroyed