Site icon TheWindowsUpdate.com

Lesson Learned #279: Slow between calls to Azure SQL Elastic Database Pool

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

It is not the first time, that we used to have this type of service requests that our customers reported slow connections in an Elastic Database Pool. Following I would like to share some details about my lessons learned about this topic. 

 

Besides following the best practices about connection and command retry-logic, connection pooling and redirection, we need too know several topics:

 

 

Knowing this, if your application is running in a single node with 20 process and those could connect to any database of your elastic database pool, for example, 80, we could see this:

 

 

In this situation, defining a specific nodes per customer or group of customers depending on business needs or/and using a proxy server that maintains the connection to the database, our users could not have this behavior. For more information, you could read this link

 

In another hand, in terms of performance, remember that an elastic database pool is a SQL Server instance that are running all the databases sharing same resources, any additional workload that one database will have could impact in the performance in others one on the same elastic database pool. 

 

Enjoy!

 

Exit mobile version