Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Sleeping Process... Expand / Collapse
Posted Tuesday, October 2, 2007 9:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 25, 2009 9:32 AM
Points: 44, Visits: 80
Can anyone get back to me with tips regarding this.

I am gettign connection pool error while using the .Net application. When i checked the Activity monitor on sql server 2005, i found that many process ID where presenet with status sleeping. When i check the details for these process ID, i found the SQL query in that. I then checked the applciation which executes the query..and found the connection is closing as well as doing a dispose() even on the connectin object. Then why does the activity monitor show so many process ID with sleeping status...??What does sleeping mean..???Any link i can refer to...??How to kill these process all togetther..??Now i restart when ever this prblem occurs..!!! or mnauly kill each process

Looking forward to your suggestions..thanks...
Post #405714
Posted Tuesday, October 2, 2007 6:17 PM


Group: General Forum Members
Last Login: Thursday, December 1, 2016 2:29 PM
Points: 1,805, Visits: 1,688
sleeping means connection is still connected to sql server.ur conection from app has not been kicked. sleeping anyway will not contribute to blocking or locking cause it will not take any table or object(resource) but take up some memory buffer.
Post #405981
Posted Monday, January 28, 2013 2:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, September 14, 2014 2:09 AM
Points: 4, Visits: 49
This is an issue that is new in SQL Server 2005, and is only exposed under specific conditions – namely,
the use of the x64 version of SQL Server 2005 and the execution of large ad hoc query batches. Unfortunately, the memory that is used to store the execution plans for those ad hoc queries is not trimmed aggressively enough in the x64 version, and as a result we see more and more connections having to wait for memory allocations before they can continue. If any connection is suspended for more than 30 seconds, the application terminates the connection by reporting that the command currently executing has timed out. This issue has been previously identified and is fixed in the upcoming service pack release (SP2) for SQL Server 2005, the Community Technology Preview (CTP) release of which is available today, and is confirmed to fix the issue in your environment.

Possible Solution:

1. Sp2
Post #1412257
Posted Monday, January 28, 2013 2:15 AM



Group: General Forum Members
Last Login: Yesterday @ 5:18 AM
Points: 45,619, Visits: 44,147
Please note: 5 year old thread.

Also, ad-hoc queries and plan cache has nothing to do with sleeping connections.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1412261
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse