|
|
Posted by TheRealPawn@gmail.com on 04/23/07 15:17
On Apr 13, 6:41 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> 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.
Navigation:
[Reply to this message]
|