We're running a licensed version of the latest version of SQL Log Rescue and are having some troubles in our most critical time (Murphy's Law). On smaller databases (50MB), I am able to run the Log Rescue (Analysis, etc). When I jump up to intermediate (in our standards) of a 500MB database, I get the famous "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." This happens during the Analysis phase.

Our C: has 13GB free, so running this on the 500MB database should not be an issue. I've even pointed the TMP environment variable to a different drive (40GB Free), but receive the same error. I'm stumped and have been working with Chris in tech support (via the phone). Any help would be greatly appreciated as we are trying to roll back a couple of transactions from this morning's event.

Did Chris send you a query to run similar to the one in the code block, below? My suspicion is that Log Rescue is hanging, not due to an over-abundance of log data, but because it can't locate the log file. In other words, if you run this query, and it doesn't ever return, then maybe there is a problem with log rescue. In one case the query never returned because the log file path was relative and Log Rescue couldn't resolve it.