# How can I diagnose database connection pool saturation?

Canonical URL: https://help.iagenify.com/faqs/databases/how-can-i-diagnose-database-connection-pool-saturation

[← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)

HELP CENTER · FAQ Databases 2 min read
# How can I diagnose database connection pool saturation?
Pool saturation occurs when available connections remain occupied and new requests must wait or fail. The cause may be a pool that is too small, slow queries, long transactions, leaked connections, or a sudden increase in concurrent work; increasing the limit without diagnosis can move pressure to the database.
IaGenify
Databases

## Measure waiting and connection use
Compare active, idle, and waiting connection counts with request volume and latency over the same period. Break the view down by application instance or workload if possible to find whether one caller is holding connections unusually long.
Inspect query duration and transaction boundaries. A transaction that includes network calls or unrelated processing can hold a connection far beyond the database work itself; ensure code paths release connections on success, error, and cancellation.
## Change capacity carefully
After identifying the bottleneck, tune the pool and database limits together using observed concurrency and the database’s safe operating range. Recheck memory, CPU, query latency, and queueing under representative load.
Add alerts for sustained waits and connection exhaustion, and document a response path. If saturation follows a deployment or traffic change, compare behavior with the previous version before raising limits. [← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)