Re: Netstat TIME_WAIT on SQL Server Connections
- From: "Mike Epprecht \(SQL MVP\)" <mike@xxxxxxxxxxxx>
- Date: Thu, 7 Apr 2005 19:14:17 +0200
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@xxxxxxxxxxxx
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jesse" <nospam@xxxxxxxx> wrote in message
news:u9T48m3OFHA.1176@xxxxxxxxxxxxxxxxxxxxxxx
> 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
>
.
- Follow-Ups:
- Re: Netstat TIME_WAIT on SQL Server Connections
- From: Jesse
- Re: Netstat TIME_WAIT on SQL Server Connections
- References:
- Netstat TIME_WAIT on SQL Server Connections
- From: Jesse
- Netstat TIME_WAIT on SQL Server Connections
- Prev by Date: OpenRowSet Connect to OLAP Problems
- Next by Date: Re: intermittent connection problems
- Previous by thread: Netstat TIME_WAIT on SQL Server Connections
- Next by thread: Re: Netstat TIME_WAIT on SQL Server Connections
- Index(es):
Relevant Pages
|