Posted by Erland Sommarskog on 04/13/07 22:41

TheRealPawn@gmail.com (TheRealPawn@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, esquel@sommarskog.se

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

• Next in forum: Re: Database Mirroring Monitor Job Error
• Prev in forum: SQL Client 2005 on Win98
• Thread view: Re: execution plan for single stored procedure from profiler

[Reply to this message]