Results 1 to 5 of 5
  1. #1
    Join Date
    Aug 2004

    Unanswered: View Transaction Log Details

    Please may I have your assistance with the following
    Im struggling to view the transaction log for a database.
    Im using the following command structure

    DBCC log ( {dbid|dbname}, [, type={-1|0|1|2|3|4}] )
    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

    Which I got from a web site, however the output does not make sense to me

    Ideally I would like to analyse which SQL insert commands are predominantly using the log file

    Any ideas how to do this or a tool that u recommend

    Thanks in advance for your help

  2. #2
    Join Date
    Jan 2003
    Provided Answers: 17
    To get a nice GUI front to the transaction log, you can try Lumigent's Log Explorer. This will only work with SQL 2000 and maybe SQL 7.0. Not sure about Yukon, or 6.5.

  3. #3
    Join Date
    Aug 2004
    Many thanks for the recomendation...
    I installed the trial version.
    Unfortunately the trial version only allows me to connect to pubs and northwind!
    Copying the database and rename to pubs or northwind is out of the question because of its size
    Any suggestions?
    Are there any means to retrieve the detail without this tool?

  4. #4
    Join Date
    Feb 2004
    In front of the computer
    Provided Answers: 54
    If you have to be able to do this post-mortem (after the fact), then buying the Log Explorer would be my suggestion.

    If you can start SQL Profiler (provided with SQL Server) before the problem occurs, you can then easily trap whatever suits your fancy and analyze it until you go blind!


  5. #5
    Join Date
    Aug 2004


    apexsql provide a full working version for 14 days.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts