Search
Home
Articles
Backup
Books
Certification
FAQ
Products
Replication
Scripts
Seminars
Training
TSQL

MSDN Fourms
Fort Worth SSUG
Oklahoma City SSDG

Resume

Champion Valley Pens

Log Explorer 1.2.1 1 2 3 4 5 6 7 8 9 10

The operations that I had performed were an insert, followed by 2 updates, followed by a delete of the same row.  Using the criteria above and clicking the create button generated the script below. This generated a script to insert the deleted row back into the database.

Using Undelete and Rollback were very confusing to me and took a lot of back and forth explanation before I finally understood them.  Since I had such a difficult time,  let me try to articulate the way things are looking in the hopes that everyone else can avoid my confusion.  When I'm looking at Log Explorer, I am seeing transactions in my log.  The transactions that I'm seeing are the ones that I'm after when I generate scripts.  I look at this from the technical perspective of "give me the transactions that I specified in my filters and let me figure out what to do with them".  From this perspective, when I enter a date, I am expecting to see the transactions that occurred BEFORE that date.  Once I have the transactions, I will decide what to do with them since I know my data and business the best.  This would mean that if I were looking at a log and I entered in the current date/time, then I would expect to see transactions generated for the entire log.  The folks at Lumigent looked at it from the opposite perspective.  They are looking at it from a recovery standpoint.  Looking at it this way, the date/time I specify is an indication of the point in time where I want to roll my data back to.  This would mean that when I enter a date/time, Log Explorer will give me all of the transactions that happened AFTER that date/time so that I can roll the data back to that point.

What makes this confusing is that I can only specify one date/time.  I can't get a begin date/time and end date/time in order to remove all of the ambiguity and also to get at a slice of my log somewhere in the middle.  We should be seeing this capability added to the product in the very near future.

Log Explorer 1.2.1 1 2 3 4 5 6 7 8 9 10

Michael R. Hotek

All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.