Home All Groups Group Topic Archive Search About
Author
29 Dec 2005 11:01 PM
PhxSam
While analyzing a production trace, I noticed that the duration on
SP:Completed was 1300 ms, but the duration for RPC:Completed was 27312 ms
(for the same proc).  I am trying to understand where this time is being
spent.  Any thoughts?

Author
31 Dec 2005 1:03 AM
David Gugick
PhxSam wrote:
> While analyzing a production trace, I noticed that the duration on
> SP:Completed was 1300 ms, but the duration for RPC:Completed was
> 27312 ms (for the same proc).  I am trying to understand where this
> time is being spent.  Any thoughts?

Probably in the client fetching. I don't generally use Duration in
SP:Completed, but I can tell you that until all rows are fetched by the
client, the RPC:Completed/SQL:StmtCompleted events are not raised.

--
David Gugick
Quest Software
www.quest.com
Author
2 Jan 2006 7:50 PM
PhxSam
Thanks.


Show quote
"David Gugick" wrote:

> PhxSam wrote:
> > While analyzing a production trace, I noticed that the duration on
> > SP:Completed was 1300 ms, but the duration for RPC:Completed was
> > 27312 ms (for the same proc).  I am trying to understand where this
> > time is being spent.  Any thoughts?
>
> Probably in the client fetching. I don't generally use Duration in
> SP:Completed, but I can tell you that until all rows are fetched by the
> client, the RPC:Completed/SQL:StmtCompleted events are not raised.
>
> --
> David Gugick
> Quest Software
> www.quest.com
>
>

AddThis Social Bookmark Button