SQL elastic pool eDTUs value getting maximum

Question

Hi

How to find the reason why SQL elastic pool eDTU value getting maximum?

Answer 1

Hi Neelakandan Durairaj (ext) •

Welcome to Microsoft Q&A forum.

As I understand, you want to know why SQL elastic pool eDTU value getting maximum?

This depends on the service tier and compute size of your Azure SQL Database elastic pools.

More detail here:

https://learn.microsoft.com/en-us/azure/azure-sql/database/resource-limits-dtu-elastic-pools?view=azuresql

The maximum number of DTUs that any database in the pool may use, if available based on utilization by other databases in the pool.

Max DTUs per database is not a resource guarantee for a database.

If the workload in each database does not need all available pool resources to perform adequately, consider setting max DTUs per database to prevent a single database from monopolizing pool resources.

Some degree of over-committing is expected since the pool generally assumes hot and cold usage patterns for databases, where all databases are not simultaneously peaking.

While the per database properties are expressed in DTUs, they also govern consumption of other resource types, such as data IO, log IO, buffer pool memory, and worker threads.

As you adjust min and max per database DTUs values, reservations and limits for all resource types are adjusted proportionally.

Min and max per database DTU values apply to resource consumption by user workloads, but not to resource consumption by internal processes.

For example, for a database with a per database max DTU set to half of the pool eDTU, user workload cannot consume more than one half of the buffer pool memory.

However, this database can still take advantage of pages in the buffer pool that were loaded by internal processes.

For more information, see Resource consumption by user workloads and internal processes.

Let us know if this helps or you have more queries.

Thanks