I am facing an issue in my SharePoint 2010 production environment, when I run SP_WHO2 query on sharepoint database instance, It gives a list of connection to different database table, in which a lot of connections are in sleeping/ awaited state. These connection include - connection to WSS_logging, COnfig, content , search and user profile DB. please see attchment -
Please suggest on below points
1. How kill these sessions from central admin if there is no impact.
2. does it take takes memory on DB server.
I think this is normal behaviour for this many connections. I say this because SharePoint will open multiple connections to SQL Server (from all servers in the farm) as there is lots of communication happening back and forth between SharePoint and SQL. That the connections are sleeping just indicates SQL Server is waiting for another command from the client. These connections should timeout after 30 seconds if no further communication is sent.
There is no way to kill these sessions from Central Administration. It technically requires memory to have these connections exist, though a sleeping connection is likely using an insignificant amount of memory (compared to a connection that is actively running queries)
Thank You Jason
I find the similar answer for my query, after searching on internet. Please help little more
1. Is connection in sleeping state comes under Microsoft best practice?
2. What will be impact if I kill those sleeping connections from database end?
- 已编辑 Pramod G 2012年8月9日 7:30