The Advanced tab shows a piece of a very interesting new feature.  When I test products, I've become very adept at using the product in such a manner that I will find the bugs that got missed during testing.  I don't go looking for them, but for some reason the way I work normally blows up an application in all the wrong places.  Along with that, I'll usually find the 1 feature that wasn't implemented but all logic would say that it should be there.  When I first picked up Log Explorer 1.0, I was told that it had the ability to recover ANYTHING from the transaction log.  Well, I understand what goes into the transaction log.  So, I processed and insert, update, and delete against a table and sure enough, Log Explorer found them and allowed me to reverse them.  Knowing that schema changes also get written into the transaction log, I performed the next thing that is catastrophic in environments.  That new person or system admin who thought they knew what they were doing connected to the wrong database and dropped one of your production tables.  Recovering from that would require restoring a database.  Well, the drop gets written to the transaction log and the data is still technically within the database and hasn't been overwritten unless a shrink operation occurred just like as was described above with recycled data.  That would mean you should be able to recover that dropped table with Log Explorer since it can recover ANYTHING from the transaction log.  Well, you couldn't do it in version 1.0.  You can now do it in version 2.0.

Log Explorer uses the structure in your database along with the data in the transaction log to generate a coherent statement in the way you are accustomed to looking at it.  You may have processed some transactions against a table that was dropped.  These transactions would be inaccessible to you, because Log Explorer would not have the table structure to work with.  The Advanced tab allows Log Explorer to retrieve the structural information from a dropped table to match up with those transactions that may have been processed against it.  It doesn't participate in the actual recovery of a dropped table, but it enables viewing transactions from a dropped table.

Log Explorer 2.0 1 2 3 4 5 6 7 8 9 10 11 12 13