Lesson Learned #155: Timeout period elapsed prior to obtaining a connection from the pool.

This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.

Connection pooling is one of the best practices that we could implement in our code due to improvement in the time spent establishing the connection. However, if we are not aware about it, we may have connectivity issues that may not be related with database service and may be related how our application closes the connection in case of any error, error handling or server client infraestructure level. 


In this YouTube session we reviewed three important points when the connection pooling is enabled: 


  • The impact establishing the connection time spent to our Azure SQL database/server.
  • What is the reason about a typical error when we reached the maximum limit of the connection pooling - Timeout period elapsed prior to obtaining a connection from the pool.
  • How to obtain connectivity pooling metrics to know how many connections, many connections pool, etc.. 


REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.