It's normal. It's used for connection pooling. It resets the
properties of the connection before reusing it from the
connection pool so that nothing persists for the next
command that uses the connection. So it's just called before
reusing the connection and isn't a bad thing. Just that call
in and of itself isn't necessarily indicative of whatever
problems you may be having. What else are you monitoring?
Did you also check the event logs on both servers?
-Sue
On Mon, 24 Oct 2005 08:11:03 -0700, Jason Morris
[quoted text, click to view] <JasonMorris@discussions.microsoft.com> wrote:
>Using a SQL2000 server on Windows 2003 linked to a SQL2000 server on NT4 we
>keep getting a sp_reset_connection on the NT4 box. I'm running a job which
>pulls data from the NT4 to the 2003 machine wrapped in a transaction. It
>seems to be closing the connection between transactions.
>It is now taking hours instead of minutes to process 200+ records.
>
>Is this normal and does it have something to do we connection pooling?
>
>Thanks
>Jason