SQL 2005 orphaned connections

Hi,
One of our customers seems to be experiancing orphaned SQL connections, which I thought was pretty much impossible with SQL 2005?

My reasoning for this is that SQL 2005 (by default) uses keep-alive requests after 30 seconds of idle time. So if the client connection is broken SQL will release all resources used by the connection.

Do we need to do something to explicitly enable this behaviour? The help suggests that it is enabled by default, as does this MS blog post;
http://blogs.msdn.com/sql_protocols/archive/2006/03/09/546852.aspx

However other people seem to have commented that SQL is sending the keep-alive, but is not doing anything when it receives no response.


Is my assumption that SQL should be able to deal with a client connectivity being lost (due to keep-alive requests)?



Andrew

.

Relevant Pages

  • Re: Concurrent database access in SQL 2005 Mobile
    ... Please stick to having an "dummy" connection in Open State. ... SQL CE/Mobile has a background thread that flushes the changes ... they run for long hours and we have not seen memory leaks so far. ... then opens his work forms and it's in ...
    (microsoft.public.sqlserver.ce)
  • Re: Concurrent database access in SQL 2005 Mobile
    ... Please stick to having an "dummy" connection in Open State. ... So it is a kind of asynchronous commit which happens every 10 ... I am not sure of this claim as we have many applications built on SQL CE ... then opens his work forms and it's in ...
    (microsoft.public.sqlserver.ce)
  • Access 2003 adp/proxy security - A substitute for SYSTEM_USER()
    ... We need a way for SQL to know the nt username that initiated the proxy ... Many stored procedures and views use a UDF that also depends on ... SyUserLogin and use HostIDand HostName() to find the right row. ... We've played with the Connection dialog settings, ...
    (microsoft.public.access.security)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)
  • Access 2003 adp/proxy security - A substitute for SYSTEM_USER()
    ... We need a way for SQL to know the nt username that initiated the proxy ... Many stored procedures and views use a UDF that also depends on ... SyUserLogin and use HostIDand HostName() to find the right row. ... We've played with the Connection dialog settings, ...
    (microsoft.public.sqlserver.connect)
Loading