SQL Server Performance

Capturing Duration in Profiler

Discussion in 'General DBA Questions' started by DBADave, Feb 24, 2006.

  1. DBADave New Member

    I'm puzzled by something I am seeing in profiler. I have one trace configured to profile the following events where Duration &gt;= 1000.<br /><br />SP<img src='/community/emoticons/emotion-7.gif' alt=':S' />tmtCompleted<br />SP:Completed<br />SQL:BatchCompleted<br />RPC:Completed<br />SQL<img src='/community/emoticons/emotion-7.gif' alt=':S' />tmtCompleted<br /><br />I'm capturing EndTime, HostName, LoginName, CPU, Reads, Writes and TextData, plus a two or three other bits of information. When the trace runs I can see a number of stored procedures and SQL statements completing in over 5 seconds.<br /><br />If I create another trace which includes the corresponding SP, SQL and RPC ...Starting Events, where Duration is &gt; 0 and run it at the same time as the above trace, I rarely see a duration &gt; 1 second.<br /><br />I can look at the same command on both profiler sessions and see different durations. Why is this happening?<br /><br />Thanks, Dave
  2. Twan New Member

    Hi Dave,

    I must admit that I've never seen this behaviour... are you able to paste small samples of thw two profiler results for the same statement?


Share This Page