468,101 Members | 1,360 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,101 developers. It's quick & easy.

execution plan for single stored procedure from profiler

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?

Apr 13 '07 #1
4 6731
On Apr 13, 6:16 pm, TheRealP...@gmail.com 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

Apr 13 '07 #2
On Apr 13, 12:03 pm, "M A Srinivas" <masri...@gmail.comwrote:
On Apr 13, 6:16 pm, TheRealP...@gmail.com 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.

Apr 13 '07 #3
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
Apr 13 '07 #4
On Apr 13, 6:41 pm, Erland Sommarskog <esq...@sommarskog.sewrote:
TheRealP...@gmail.com (TheRealP...@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, esq...@sommarskog.se

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.

Apr 23 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Dimitri Furman | last post: by
10 posts views Thread by J. S. EDV | last post: by
1 post views Thread by Solo | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.