February 21, 2002 at 2:35 am
Is there a way to kill connections that haven't been used for x minutes?
I am experiencing a situation where the number of connections has more than doubled with no increase in users, and it seems that old connections are remaining open. This has occured after updating the network driver on the SQL server, if thats at all possible!
Any assistance appreciated
February 21, 2002 at 4:57 am
You would write a script (heck, we might have one in the library) that would query sysprocesses and figure out which spids to kill. Before you do that I think it's worthwhile to find out why it's happening though. If you're using ASP I think it has a timeout that can be modified. In code make sure you're closing all connections and setting to nothing.
Andy
February 21, 2002 at 6:05 am
I figured it out - the new network driver setting was on half duplex, causing collisions which resulted in orphaned sessions
February 21, 2002 at 11:05 am
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply