Open for Voting
over 1 year ago

Better monitoring for Azure SQL Elastic Pools

While there is support for monitoring Azure SQL Databases, the problem is that every Azure SQL Database is added as an entirely separate target.

Unfortunately, this means that we don't have a server-level view of an Azure SQL Logical Server and Elastic Pools.

This becomes paramount in Elastic Pools, when "noisy neighbors" can potentially affect the performance of all databases in the same pool. But with SQL Sentry it's quite impossible to quickly pinpoint which database is the noisy one and why.

Can anything be done to make it easier to monitor Azure SQL Elastic Pools and troubleshoot performance problems at the pool level?