I have a question about "sleeping" processes.
We have an application that access our SQL Server. I just took a look at the Current Activity and I saw 18 processes from the same person that all had a login time of a few seconds.
I have seen this before where I have had a large number of sleeping processes that had login times and last batch times that were long ago.
Is this caused by opening connections and not closing them, or is it something else? Also, should I be concerned about having a lot of sleeping connections? Is it going to cause a big drain on my system? If so, should I do something about killing sleeping processes after a certain time or will this cause bigger problems?
This can be somewhat confusing when looking at sp_who in Query Analyzer. I believe this is somewhat of an energy saver feature. When a spid is sleeping it is simply holding a place holder representing a login against the database. It is very common to see many processes with a status of sleeping even from Production application processes. I do not believe these processes are holding locks nor do they affect performance.
Oh, btw, GO HOGS!
Normally a sleeping process may be waiting ether for a lock or user input. Cortec is correct the process is not holding locks.
We walk in the dark places no others will enterWe stand on the bridge and no one may pass