|
|
|
|
|
Log Explorer 1.2.1 1 2 3 4 5 6 7 8 9 10 Once you have connected to a server and database, you are now ready to begin working with the transaction log or backup file. The Log Summary as shown below will give you the high level details of the transaction log you are working with.
The majority of the work you will do is within the transaction log itself. Lumigent has provided a very flexible set of criteria to allow you to filter out the section of the transaction log that you are interested in. You can specify where in the log you want to begin looking and the direction that you want to browse in. Transaction logs consist of logical blocks internally that are sequentially used by SQL Server. At the same time, the transaction log is circular in nature. As transaction log backups are completed, the storage area of the log that was backed up can be reused. This allows the transaction log to move forward and when it reaches the end of the space currently allocated, it can begin writing entries back over the space that has been freed due to a back up. This space still contains actual information that will be sequentially overwritten. The default setting for Log Explorer is to ignore the portion of the log that can be recycled to prevent "corrupt" data from being displayed whereby SQL Server may overwrite an area of the log that is currently being viewed.
|
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.
