The file menu as shown below gives you some basic functionality.  But, don't be fooled by it.  The save item I'll return to later when discussing the Recover menu item since it performs the same function and this is the heart of the Log Analyzer.   Change Database allows you to switch your database context.  The Read Log from File is a very powerful feature.  This allows you to take a tran log dump and reload it into the Log Analyzer.  This gives you the ability to reverse engineer transactions that are no longer part of the currently active log.  You have to be careful with this though since the Log Analyzer gets information from the current database and server.  If you load a dump file from a database/server other than the one you are currently connected to or you have made significant schema changes, data errors can occur.

The preferences menu gives you a dialog box as shown below where you can set two basic options.  By default the Log Analyzer will start at the top of the tran log which contains your oldest transactions.  You are generally interested in the most recent transactions, so the Start at End of the Log option should be turned on.  The View filtered log will elminiate a few items from your display that you can't interact with any way such as the oam pages.  This should also be turned on for most production work.

The edit menu as shown below is relatively worthless.  The list box is editable, but nothing can be saved from it.  Making changes to this activates the undo command.   The cut, copy, and paste also work for text selected within the list box which is pretty worthless.  It does have one saving grace.  The find comes in very handy.   The log I'm displaying here is very small.  A tran log on a production server can be several thousand screens long.  If you need to find a particular entry or object, the find is invaluable.

Log Analyzer 2.02 1 2 3 4 5 6