Review: Recover from Almost Anything with Log Explorer 3.0
-
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/bknight/lumigentlogexplorer3.asp
Brian Knight
Free SQL Server Training Webinars -
I agree this is a great tool. We ran a lot of tests and simulated several disasters, all of which we recovered from. The interface is not entirely intuitive. For example, the only way I found to rollback a single transaction was to right click on the transaction.
Brian points out that foreign keys might have to be dropped when restoring information. To that I would add that you might need to disable triggers to properly restore the data. Small potatoes considering the value of the recovery but should be kept in mind anyway.
-
Couldn't agree with Brian more. This is a great product! Great review!
David
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
-
Thanks for the comments Ron. I too tried to "break" the program as best I could and couldn't do it
. It seemed that in most cases of a breakage it was a user problem like loading orphaned records in. I tend to agree that the interface needed some work in the area you mentioned but I wonder if it's more of a technical reason versus an interface reason why that couldn't do that.Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars -
Brian,
Generally good review - but this point is no longer true as of 10/2003
"Viewing the transaction log (only product on the market that can do that) "
There is another product on the market that can do this LockwoodTech Log Navigator - http://www.lockwoodtech.com/index_lognavigator.htm
Log Navigator currently supports data change audits only but support for DDL and Select auditing is planned soon.
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
. It seemed that in most cases of a breakage it was a user problem like loading orphaned records in. I tend to agree that the interface needed some work in the area you mentioned but I wonder if it's more of a technical reason versus an interface reason why that couldn't do that.Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply