Can connection pool helps on too sudden spike in INACTIVE sessions
Hi, I've been facing some problem on my production database from time to time. All of the suddenly I receive an alert of a huge spike in INACTIVE sessions within a few minutes causing my database max out the processes & sessions. Most of the culprit comes from application servers running W3WP.exe processes. Apps guys can't explain why it suddenly created so much connection to the DB. From my end I don't think i can force INACTIVE connections to timed out, as this will cause problems on applications that genuinely behave such way.
I've been googling around and come onto the suggestion on using connection pooling on application level. This way there will be only a fix amount of sessions connected to the DB and all other sessions will be retain from the middle tier. Does this works? And can IIS (W3WP) be configure such way? -