Netstat TIME_WAIT on SQL Server Connections

If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on the
server indicates that the connection has been closed, and it is waiting to
clear. Is that right? If so, we have a lot of SQL Server connections that
are in TIME_WAIT status mode. We may have well over 100 or so of these, and
they do not clear out very fast. Why would they stick around like that, and
how do I get them to clear out sooner? Could they potentially be causing
problems by not clearing out?
Thanks,
Jesse
Hi
Connection Pooling on the Client MDAC stack. By default the SQL Driver will
keep the connection open for 120 seconds after a "close" has been issued. If
another request comes along and it uses the same credentials to the same
server, it does not have to re-setup the TCP/IP connection. Instead it puts
it on the connection that has been around the longest in the TIME_WAIT
state.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jesse" <nospam@.fake.com> wrote in message
news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
> If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on
> the server indicates that the connection has been closed, and it is
> waiting to clear. Is that right? If so, we have a lot of SQL Server
> connections that are in TIME_WAIT status mode. We may have well over 100
> or so of these, and they do not clear out very fast. Why would they stick
> around like that, and how do I get them to clear out sooner? Could they
> potentially be causing problems by not clearing out?
> Thanks,
> Jesse
>
|||I have looked into those settings, and they are set up as you stated,
however, these are staying in TIME_WAIT long after the 120 seconds. For
instance, I can log on to our server at 8:00 or 9:00 at night, when there is
no one on the server, and there are well over 100 connections left in
TIME_WAIT status. Any ideas why?
Jesse
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ol4H%23U5OFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hi
> Connection Pooling on the Client MDAC stack. By default the SQL Driver
> will keep the connection open for 120 seconds after a "close" has been
> issued. If another request comes along and it uses the same credentials to
> the same server, it does not have to re-setup the TCP/IP connection.
> Instead it puts it on the connection that has been around the longest in
> the TIME_WAIT state.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Jesse" <nospam@.fake.com> wrote in message
> news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
>