Connection Pooling TCP protocal

Client (TCP and Named Pipe) Connection Pooling

http://kennyw.com/indigo/181

The way connection pooling works on the client is as follows:

• When you open a channel we will first look for a connection in our pool. This lookup is performed based on IP+port for sockets and based on endpoint Uri name for Pipes.
• If we find an available connection in our pool then we will attempt our open handshake using .Net Framing. If this succeeds then we will associate the connection with the new channel and return from Open. If it fails then we’ll discard the connection. If we have not yet exceeded the binding’s OpenTimeout then we will repeat the “look in pool” process.
• If no [valid] connections are found in our pool then we will establish a new connection (again, using up to the time remaining in OpenTimeout).
• When you close a channel, after we perform our close handshake we will consider returning the connection to our pool. If we already have reached MaxOutboundConnectionsPerEndpoint, or the connection’s lifetime has exceeded LeaseTimeout then we will close the connection instead. The connection that is returned to the pool is the “raw” connection (the one that was initially accepted, prior to any security upgrades). In this way we can provide a transparent pool without leaking any security or other information.

 

http://blogs.msdn.com/b/sql_protocols/archive/2006/03/09/546852.aspx

Understand special TCP/IP property “Keep Alive” in SQL Server 2005