RPC:Starting will screw up the Duration Filter functionality

Last Post 19 Feb 2007 12:33 PM by SQLUSA. 3 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
blizzard_SQL
New Member
New Member

--
16 Feb 2007 06:49 AM
Hello,

I was trying to capture slow sqls so I had the following:

Events:
RPC:Starting
RPC:Completed
TSQL:BatchCompleted

I then added the duration filter, for example, greater than 20000. But what happened is that I only see RPC:Starting event all over the trace with Duration column empty with no values. If I remove RPC:Starting event then I got Duration column correctly filled up with values bigger than 20000. On the other hand, if I remove the Duration filter and keep the above events, then I also see all 3 events, although now it's for everything rather than what I want to see--slow sqls running longer than 20 seconds!

Has anyone come across this before?

Thanks,

Harry

JHunter
New Member
New Member

--
16 Feb 2007 07:25 AM
Duration is not available with the starting event, it would always be zero anyway.

Just recording the complete events with the filter will show you everything you all the long running procs.

Jamie
SQLUSA
New Member
New Member

--
19 Feb 2007 12:33 PM
It is sufficient to use the COMPLETED event. Since using the duration, you can calculate the start.

Remember the duration is msec i.e. 4 sec --> 4000

Kalman Toth
SQLUSA: http://www.sqlusa.com
JHunter
New Member
New Member

--
20 Feb 2007 01:27 AM
quote:

Originally posted by: SQLUSA
It is sufficient to use the COMPLETED event. Since using the duration, you can calculate the start.



Wasn't that what I implied?

There are Start Time and End Time Columns available on the *Completed events...

Jamie
You are not authorized to post a reply.

Acceptable Use Policy