Re: SQL 2005 orphaned connections
- From: "Andrew Teece" <enate@xxxxxxxxxxxxx>
- Date: Wed, 16 Apr 2008 09:58:00 +0100
Charles,
This seems to contradict what the SQL Server help states.
My understanding is that SQL 2000 does not use keep-alive packets unless the OS TCP/IP stack is configured to do so, but SQL Server 2005 sends keep-alive packets at an interval defined in the server protocols configuration dialog. The default being 30,000 (30 seconds). SQL uses the system values for the keep alive interval (default 1000) and Max Data Retransmissions (default 5). This means that the orphaned connection will be detected in 35 seconds (1 keep alive + 5 retransmissions of keep alive packet).
Most of this is from the blog post from the SQL blog post I mentioned earlier.
On our internal test platform I can see the keep-alive requests being sent by using a packet sniffer (and the registry settings for TCP/IP have not been modified) although I dont have the same level of access to our customers platform to use a sniffer.
If SQL Server 2005 uses the sytem configured keep-alive value (ergo we must have keep-alive enabled for all TCP/IP connections) what is the purpose of the SQL keep-alive value in the TCP/IP protocol dialog?
Andrew
"Charles Wang[MSFT]" <changliw@xxxxxxxxxxxxxxxxxxxx> wrote in message news:eyAuJ3snIHA.1036@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Andrew,
Sending keep-alive packets indeed happen, but not at SQL Server application
level. Windows operating system will do it according to the mechanism of
managing client connections of the lower level IPC. I recommend that you
refer to this KB article for a clear view:
How to troubleshoot orphaned connections in SQL Server
http://support.microsoft.com/kb/137983/en-us
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
.
- Follow-Ups:
- Re: SQL 2005 orphaned connections
- From: Charles Wang[MSFT]
- Re: SQL 2005 orphaned connections
- References:
- SQL 2005 orphaned connections
- From: Andrew Teece
- RE: SQL 2005 orphaned connections
- From: Charles Wang[MSFT]
- SQL 2005 orphaned connections
- Prev by Date: Re: SQL 2005 orphaned connections
- Next by Date: Re: SQL 2005 orphaned connections
- Previous by thread: RE: SQL 2005 orphaned connections
- Next by thread: Re: SQL 2005 orphaned connections
- Index(es):
Relevant Pages
|
Loading
