execution plan for single stored procedure from profiler

[TheRealPawn]

I'm trying to get the execution plan for a single stored procedure
from Profiler. Now, I've isolated the procedure but I get all
execution plans. Any ideas on how to connect the SPIDs so that I only
get the execution plan for the procedure I'm watching and not the
whole of the server?

[M A Srinivas]

On Apr 13, 6:16 pm, [e-mail] wrote:

I'm trying to get the execution plan for a single stored procedure
from Profiler. Now, I've isolated the procedure but I get all
execution plans. Any ideas on how to connect the SPIDs so that I only
get the execution plan for the procedure I'm watching and not the
whole of the server?

You can try use filter on objectname like or if you are executing
from QA , provide the SPID

[TheRealPawn]

On Apr 13, 12:03 pm, "M A Srinivas" <[e-mail]:

On Apr 13, 6:16 pm, [e-mail] wrote:

I'm trying to get the execution plan for a single stored procedure
from Profiler. Now, I've isolated the procedure but I get all
execution plans. Any ideas on how to connect the SPIDs so that I only
get the execution plan for the procedure I'm watching and not the
whole of the server?

You can try use filter on objectname like or if you are executing
from QA , provide the SPID

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.

[Erland Sommarskog]

Th*********@gmail.com (Th*********@gmail.com) 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, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[TheRealPawn]

On Apr 13, 6:41 pm, Erland Sommarskog <[e-mail]:

[e-mail] ([e-mail]) 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, [e-mail]

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.