The symptom of a timeout when retrieving a pooled connection can be due to various causes. Assuming the application does properly close/dispose connections (e.g. with a using block in C# or VB.NET), the symptom can be caused long-running queries (extended blocking or query/index tuning needed), undersized database tier, undersized, application tier, or slowness in retrieving large result sets.
Examine activity during the problem timeframe to determine next steps to resolve.
Database tier : Standard S1: 20 DTUs. No elastic pool
Hey, Are you able to access the database now ? Meaning was that error intermittent or is it still persistent?
And from where are you trying to access database? And code application?
If yes, In most cases connection pooling problems are related to connection leaks. Your application probably doesn't close its database connections correctly and consistently.
error intermittent and connecting from an outsystem application
Similar reference :
stackoverflow.com/questions/670774/how-can-i-solve-a-connection-pool-problem-between-asp-net-and-sql-server?rq=1
Sign in to comment