April 11, 2006 at 12:54 pm
One of our clients has been told by their ISP that there are excessive sleeping processes on their SQL Server and that we need to kill them.
Frankly this sounds like they are saying "we have no idea why your server is slow but it isn't our problem".
There doesn't seem to be many processes on the box at all which sort of reinforces my point but am I right?
April 11, 2006 at 3:03 pm
Excessive sleeper process can mean you are not closing your connections correctly so that can be reused in connection pooling and thus they also never die. When you open a connection you have to properly close it or it will remain active and slow use more and more system resources to be maintained and thus slow your server and/or prevent connections altogther. A common practice is to just issue a kill on the SQL Server side but is a band-aid at best. You need to check your code and make sure each time you open you close the connection correctly depending on your programming language.
April 13, 2006 at 8:23 am
run the sp_who2 command on the SQL Server to try and see how many users are running on the database server.
use the kill (spid) to remove any connections which have been inactive for some time.
As above this is no resolution to the problem. I would go through your code and check that you are closing all your ADO connections.
June 12, 2007 at 2:51 pm
Does anyone know how long SQL server takes before it kills inactive connections? Thanks.
Chris
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply