Post reply

SP_TRACE_CREATE File Much Larger than Its Profiler Counterpart

  • July 20, 2007 at 10:32 am

    #174520

     

    The sql traces that are running on my database server via a stored procedure (essentially scripted out from the GUI profiler trace that were previously running from my local workstation) can result in .trc files being 10x as large as the file created if I run profiler from a workstation.  Example of scripted trace that is executed on the database server:  61000 rows of data (and all columns selected) of the below parameters result in a .trc file over 1.3GB.  Isn't that way large?

     

    Database

    -Log File Auto Grow

     

    Locks

    -Deadlock Graph

    -Lock: Deadlock

    -Lock: Deadlock Chain

    -Lock: Timeout

     

    Stored Procedures

    -RPC: Completed

    -SP: Completed

     

    Granted the server based sp_trace_create is capturing all events (versus missing some on the workstation based profiler) but it is odd that only 61000 rows produce such a large file.

     

    Furthermore, if I open up one of these 1.3GB .trc files on the database server and SAVE AS a different name, the resulting size is over 2GB.  Should I be testing my systems for (mad-hatter) Hg poisoning?  Probably test myself while I'm at it.

     

    SS2005 9.00.3159 (X64), Enterprise Edition, 2 node cluster, Win2003 SP2

     

    Gracias for your assistance!

     

  • July 25, 2007 at 8:25 am

    #722309

    off the top of my head the difference could be due to block size of the disks. It's possible that 64bit values may be larger than 32 bit values giving a difference.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

Viewing 2 posts - 1 through 1 (of 1 total)

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