July 23, 2003 at 1:11 pm
I want to run this by everyone to make sure that I'm interpreting this correctly. I'm trying to differentiate between the duration in the SP:Completed event and the RPC:Completed event. Is it true to say that the duration in the SP:Completed event is the amount of time that the stored procedure took to execute, and the duration in the RPC:Completed event the amount of time that it took to execute the stored procedure and return the result set to the caller?
TIA for your input.
July 23, 2003 at 1:44 pm
PS:Completed indicates the stored procedure has completed. RPC:Completed occurs When one instance of SQL Server send a request for another SQL Server to execute a remote procedure, the relational engine recognizes it, and shows in the profiler as RPC:Starting and RPC:Completed when it completes
Shas3
July 23, 2003 at 1:57 pm
Let me phrase my question another way, based on things that I'm seeing in profiler traces. We have a web application (IIS/ASP) that calls a COM layer, which executes a stored procedure and returns the results to the caller. The call from the web server to SQL Server, of course, shows up as an RPC. When I run a profiler trace looking at both RPC:Completed and SP:Completed, I'm finding that the duration times are nearly equal. So, I'm assuming that the duration includes the amount of time that it takes to execute the stored proc and return the results to the caller. What I'm seeing in the profiler traces are duration times that are much longer than if I execute that same stored procedure directly in Query Analyzer. So, I'm trying to find out what is taking the extra time. But, before I do that, I want to make sure that I'm interpreting the profiler output correctly.
Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply