|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Profiler QuestionWhile 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? PhxSam wrote:
> While analyzing a production trace, I noticed that the duration on Probably in the client fetching. I don't generally use Duration in > 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? 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. 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 > > |
|||||||||||||||||||||||