Re: Odd maximum elapsed event times in raw 10046 trace

Agreed. I think that the app is munching the data during this time and waits to complete this before disconnecting.

The sequence of events (waits on different cursors and commits) still seems peculiar.

Thanks again.

Mat.

niall.litchfield_at_dial.pipex.com (Niall Litchfield) wrote in message news:<b6beca79.0408060508.64d5f961_at_posting.google.com>...
> mathewbutler_at_yahoo.com (Matt) wrote in message news:<19f48a45.0408032226.1c874ffb_at_posting.google.com>...
>
> > Looking in the raw trace file, I see that the maximum duration event
> > (ela= 1711972045) is right at the end of the trace (as if the
> > application was just waiting for something to happen):
>
> Oops. It may of course be that it is just waiting for the client to disconnect...
Received on Sun Aug 08 2004 - 20:17:07 CDT