Home Forums Article Discussions Article Discussions by Author Discuss content posted by Brad M. McGehee Mastering SQL Server Profiler - Part 5: Data Columns RE: Mastering SQL Server Profiler - Part 5: Data Columns

  • March 30, 2010 at 2:30 pm

    #1142695

    Stefan_G (3/30/2010)

    You probably have lots of overlapping queries. If your application generates 20 simultaneous queries that all start at 00:00:00 and then all finish at 00:00:02 the elapsed time would be 2 seconds, but the sum of all durations would be 40 seconds.

    That's it. Here is a small sample of three overlapping queries.

    Event ClientProcessID SPID StartTime EndTime Duration TextData

    SQL:BatchCompleted5740 74 12/1/2009 10:13:01.660 12/1/2009 10:13:01.713 52003 Query1

    SQL:BatchCompleted5596 68 12/1/2009 10:13:01.660 12/1/2009 10:13:01.713 52003 Query2

    SQL:BatchCompleted812 73 12/1/2009 10:13:01.660 12/1/2009 10:13:01.713 53003 Query3

    Thanks, Stefan_G.

    So in the end, it looks like you should not rely on the sum of the duration column if you want to compare the total SQL duration time with the total elapsed time.