|
|
|
|
|
Log Explorer 1.2.1 1 2 3 4 5 6 7 8 9 10 When you are dealing with relatively small transaction logs (200MB or less), you can probably get away with an unlimited search depth. However, you can get overwhelmed very quickly because a transaction log contains large volumes of entries. Even a small transaction log can have hundreds of thousands of entries. I strongly discourage trying to view a transaction log without using any filter criteria. Viewing without filter criteria would simply be for curiosity sake because of the information overload that you would get.
Once you have completed the filter criteria, clicking the View Log button will show the actual display of the transaction log. You will notice a second pane on the bottom of the screen shown. When you select entries on the log that deal with data changes, the actual data will be displayed in this pane allowing you to browse the change that was made in a format that is easily understood. The transaction log that I am using here is for the pubs database where I have executed 4 transactions. As you can see, these four transactions generate a lot of activity in a transaction log. By being able to gauge the actual volume of entries that are made in a transaction log for even a trivial number of transactions, gives you a good idea why people have recommended placing the transaction log on a separate set of physical disks optimized for sequential writing in order to improve performance.
|
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.
