Re: execution plan for single stored procedure from profiler
- From: "TheRealPawn@xxxxxxxxx" <TheRealPawn@xxxxxxxxx>
- Date: 23 Apr 2007 08:17:29 -0700
On Apr 13, 6:41 pm, Erland Sommarskog <esq...@xxxxxxxxxxxxx> wrote:
TheRealP...@xxxxxxxxx (TheRealP...@xxxxxxxxx) writes:
Well, we have it filtered down to stored proc and execution tree via
the text data. However, we get all execution tree data not just for
the execution of the stored proc. We won't know the SPID and is very
likely we'll have many SPIDs that we'll see in the trace.
You should be able to filter for the ObjectID of the stored procedure. (And
database ID if there are multiple databases with the same object ID.) At
least that works on SQL 2005. (I know, because I set up such a trace at a
customer site. Proabably still running, because I have had had little time
to look at it!)
--
Erland Sommarskog, SQL Server MVP, esq...@xxxxxxxxxxxxx
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Unfortunetly, I resigned myself to that there is not good answer to
this in SQL 2000. Thanks for all the help.
.
- References:
- execution plan for single stored procedure from profiler
- From: TheRealPawn
- Re: execution plan for single stored procedure from profiler
- From: M A Srinivas
- Re: execution plan for single stored procedure from profiler
- From: TheRealPawn@xxxxxxxxx
- Re: execution plan for single stored procedure from profiler
- From: Erland Sommarskog
- execution plan for single stored procedure from profiler
- Prev by Date: Re: READ UNCOMMITTED data
- Next by Date: Re: Update trigger or ?
- Previous by thread: Re: execution plan for single stored procedure from profiler
- Next by thread: sqlconnection open state
- Index(es):
Relevant Pages
|
Loading