Transaction log reading tools

  • Hi,

    I was wondering if there are any good transaction log reading tools or commands available. I checked out the article on LOP PI on this website, and was impressed by its capabilities, but apparently their website is not opening.

    Can someone give me pointers to good Tran log reading techniques.

    Thanks.


    What I hear I forget, what I see I remember, what I do I understand

  • We use Lumigent Log Explorer.  It does a good job of making sense of what's recorded in the t-log whether you're looking at a current log or a backup.  See it at http://www.lumigent.com/

    If you're a do-it-yourselfer, you can use DBCC LOG.  It's not as useful as a third-party tool, but it's free.

    DBCC log ( {dbid|dbname}, [, type={-1|0|1|2|3|4}] )

    PARAMETERS:

       Dbid or dbname - Enter either the dbid or the name of the database

                        in question.

          type - is the type of output:

          0 - minimum information (operation, context, transaction id)

          1 - more information (plus flags, tags, row length)

          2 - very detailed information (plus object name, index name,

              page id, slot id)

          3 - full information about each operation

          4 - full information about each operation plus hexadecimal dump

              of the current transaction log's row.

         -1 - full information about each operation plus hexadecimal dump

              of the current transaction log's row, plus Checkpoint Begin,

              DB Version, Max XACTID

    by default type = 0

    To view the transaction log for the master database, you can run the

    following command:

    DBCC log (master)

    Greg

     

    Greg

  • Thanks for the link Greg.

    Was aware of the DBCC log function but I am not too pleased with its out put. Rather I am unable to use to output according to my requirements.


    What I hear I forget, what I see I remember, what I do I understand

  • The dblog virtual function produces nicer output than DBCC Log. Specifically, since it's part of a query, it's easy to filter, group, etc

    SELECT

    * FROM ::fn_dblog(null,null)

    The two params are the first and last LSNs

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply