Log Rescue would definitely not be the tool to use in this case. It assumes that you have a fully-working, consistent database. The way in which it helps recover data in the case of a disaster is if an unwanted query had been run, for instance:
- You had been the victim of the fables SQL Server 'injection' attack
- A rogue (or poorly trained) employee enters a query with no WHERE clause
- An administrator 'accidentally' drops a table
If the database is unavailable or broken in any way, it would be difficult or impossible to use Log Rescue with it, but if the database is functional and some data had accidentally been updated or deleted, it would be the tool to use to get it back.