Re: run Profiler on a specific SP/Query/Function
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 17 Apr 2006 08:08:19 +0000 (UTC)
Michael Hotek (mike@xxxxxxxxxxxxxxxxxxxxxxxx) writes:
Also, I find the RPC: Starting and the TSQL:BatchStarting events to be
virtually worthless and never use them. I always use the RPC: Completed
and TSQL: BatchCompleted events, because you get duration, reads,
writes, and CPU which are critical stats when trying to analyze
anything.
Depends. The Starting events can be useful if you want to see how things
interact, so you get a better grip over the flow. Also, I have a feeling
that you don't always get a Completed event if the batch is aborted due to
an error. (But I have not examined this in detail.)
But I far more often exclude them than include them in traces, that's true.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: run Profiler on a specific SP/Query/Function
- From: Greg Linwood
- Re: run Profiler on a specific SP/Query/Function
- References:
- Re: run Profiler on a specific SP/Query/Function
- From: Greg Linwood
- Re: run Profiler on a specific SP/Query/Function
- From: Michael Hotek
- Re: run Profiler on a specific SP/Query/Function
- Prev by Date: Re: Error in Query Analyzer when I try to execute an update Msg 36
- Next by Date: Re: Exception trying to import data from Excel .
- Previous by thread: Re: run Profiler on a specific SP/Query/Function
- Next by thread: Re: run Profiler on a specific SP/Query/Function
- Index(es):
Relevant Pages
|
