MS SQL keeps randomly faulting, gateway disconnecting randomly

[JordanCClark]

From this line:

Cannot get a connection, pool error Timeout waiting for idle object

This exception is stating that the pool manager cannot produce a viable connection to a waiting requester and the maxWait has passed therefore triggering a timeout. Usually the issue falls into two broad categories:

1. The DB is down or unreachable. This could be because you forgot to start it, or it crashed, or the network between you and the DB has stopped working.

2. The connection pool is out of connections. This could be due to high demand, or it could be an indication of a connection leak where connections are never returned to the pool and eventually you exceed the max connections limit.

Using Perfmon to find bottlenecks in SQL Server

The information below is to be used as a guide. Just because the counters collected in your environment may be drastically different from those listed below does not mean that there is a problem. I am sure many of these could be debated but I find the information helpful and you can be the judge if it is useful in your environment(s). I am not the author of the content below so if you see something that you disagree with… don’t blame me! Memory Bottleneck Analysis Object: - Memo…