|
|
|
|
|
Log Explorer 2.0 1 2 3 4 5 6 7 8 9 10 11 12 13 Log Explorer gives you the flexibility to customize the columns of data displayed so that you are only working with that data which you feel is pertinent. I normally leave this at the defaults, however in certain situations I may add the System User ID along with the LSN (Log Sequence Number).
You can also connect to your database server using either Named Pipes or TCP/IP.
The first thing you do is connect to a server as shown below.
Once connected, you can select the database that you wish to use and then specify whether you want to look at the live, online transaction log, 1 or more transaction log backups, or both. This is one of the first major changes that Lumigent has made. In version 1.0, you could only select 1 backup file. That worked great until you tried it on a system that backs up the transaction log every 2 minutes. You can now select as many backup files as you want and Log Explorer will correctly chain them together into a single coherent view. You must be very careful when you connect to the database server and you must connect to one. This may seem odd to many. The transaction logs contain the raw data that is written to the server. They do not contain any of the structural data such as the database schema. Log Explorer combines the data in the transaction log with the database structure to produce a coherent transaction trace. If you attach to a database whose schema significantly varies from the schema that the transaction log was produced against, you can have some serious problems.
|
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.
