September 8, 2003 at 10:00 am
On our SQL Server 2000 sp3, I have noticed that the applications that are connecting are no longer being dropped at the end of the business day like they use to. The programmers have claimed they did not change their code to keep an open connection. These SPIDS hang for over a week(over 300) and I am concerned that the connection pool is not being properly utilized.
The only change for Windows 2000 was installing SP4 on both COM+/ISS and SQL Server boxes.
Setting are:
Max Worker Threads = 255
Maxium Concurrent User Connections = 0
Not using Windows NT Fibers
No error messages are returned on client side.
Thank you in advance for your input!
September 8, 2003 at 3:00 pm
Have a look at the end of this article at
September 8, 2003 at 5:57 pm
You may want to take a look at the following article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;137983
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
October 3, 2003 at 2:56 pm
it appears that out of 103,945 database professionals on this site that none relate to hanging spids issues that I have.
My conclusion is that Windows 2000 sp4 and COM+ do not let go of these connections since this issue did not occur on sp3. It could be another MS bug. I have locks on all these spids and could just reboot and start fresh every week to clear them out and at the same time reinitialize COM+ too.
November 25, 2003 at 6:10 pm
Here is an update. It was not a MS bug or sp4 but COM+ could not disconnect because of the programmers lack of wrapper code. I had these dll's dropped into the IIS and the database connections behaved the same way by creating an 'in-state' instead of stateless connection. Now I have set up a job to automatically disconnect these hanging spids at the end of the day until they get their code fixed.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply