SQL Elastic Pools Not Responding - Timeout error / unable to access table via SQL Management Studio

Question

SQL Elastic Pools Not Responding - Timeout error / unable to access table via SQL Management Studio

Grant Jaquest 20

Hi

We have a number of SQL pools that are having access issues.

As you can see from the Resource utilization chart there are periods of missing "tracking" :

User's image

Grant

******@brightlogic.co.uk

Pilladi Padma Sai Manisha 8,730 Reputation points Microsoft External Staff Moderator

2026-05-13T10:55:09.6733333+00:00

Hi Grant Jaquest,
Thankyou for reaching microsoft Q&A!
Could you please share requested details in private message.
Pilladi Padma Sai Manisha 8,730 Reputation points Microsoft External Staff Moderator

2026-05-28T11:46:03.07+00:00
Hi Jaquest,
From the details shared, the issue appears to be related to intermittent unresponsiveness of the SQL Elastic Pool, which is causing connection timeouts and failures when accessing databases/tables through SSMS.

The gaps in the Resource Utilization graph usually indicate that the service was temporarily unable to report metrics, often because the pool was under heavy load, experiencing connectivity interruptions, or recovering from resource pressure. During these periods, queries and connections may fail or time out.

To narrow this down, could you please help with the following:

Confirm whether the issue affects all databases in the elastic pool or only specific ones.

Share the approximate UTC timeframe when the issue was observed.

Check if CPU, DTU/eDTU, storage, or worker percentage reached close to 100% during the incident.

Let us know if there were any long-running queries, blocking, or maintenance jobs running at that time.

Please share the elastic pool name and region.

As an initial mitigation, you may also try:

Scaling up the elastic pool temporarily.

Reviewing Query Performance Insight / Intelligent Insights for spikes.

Checking for blocking or deadlocks using DMVs.

Once we have the above details, we can help determine whether this is resource exhaustion, transient platform connectivity, or a workload-related issue.

1 answer

Your answer

Pilladi Padma Sai Manisha 8,730 Reputation points Microsoft External Staff Moderator

2026-05-13T10:55:09.6733333+00:00

Hi Grant Jaquest,
Thankyou for reaching microsoft Q&A!
Could you please share requested details in private message.
Pilladi Padma Sai Manisha 8,730 Reputation points Microsoft External Staff Moderator

2026-05-28T11:46:03.07+00:00

Hi Jaquest,
From the details shared, the issue appears to be related to intermittent unresponsiveness of the SQL Elastic Pool, which is causing connection timeouts and failures when accessing databases/tables through SSMS.

The gaps in the Resource Utilization graph usually indicate that the service was temporarily unable to report metrics, often because the pool was under heavy load, experiencing connectivity interruptions, or recovering from resource pressure. During these periods, queries and connections may fail or time out.

To narrow this down, could you please help with the following:

Confirm whether the issue affects all databases in the elastic pool or only specific ones.

Share the approximate UTC timeframe when the issue was observed.

Check if CPU, DTU/eDTU, storage, or worker percentage reached close to 100% during the incident.

Let us know if there were any long-running queries, blocking, or maintenance jobs running at that time.

Please share the elastic pool name and region.

As an initial mitigation, you may also try:

Scaling up the elastic pool temporarily.

Reviewing Query Performance Insight / Intelligent Insights for spikes.

Checking for blocking or deadlocks using DMVs.

Once we have the above details, we can help determine whether this is resource exhaustion, transient platform connectivity, or a workload-related issue.

Answer 1

hi Grant Jaquest & thanks for join me here at Q&A portal,

the missing metric points in the chart are a red flag. If several elastic pools become unreachable at the same time and Azure Monitor has gaps, treat it as possible Azure SQL platform or regional issue first, not just SSMS. Look at Azure Service Health for the SQL region and open a support case with the exact UTC time window. Include the screenshot, server names, elastic pool names, database names, timeout errors and Activity Log entries.

For pool-side checks, look at CPU, Data IO, Log IO, workers, sessions and DTU or vCore utilization. Actually Azure SQL elastic pool metrics are documented https://learn.microsoft.com/en-us/azure/azure-sql/database/monitoring-metrics-alerts?view=azuresql

Elastic pools share CPU, memory, workers, storage and tempdb, so one noisy database can affect others in the same pool https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-resource-management?view=azuresql

If only SSMS is timing out but apps still work, increase connection timeout and test from another network. If apps and SSMS both fail, and metrics have gaps, escalate as Azure SQL availability or telemetry issue.

https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues?view=azuresql

I guess it is missing monitoring data plus timeouts across multiple pools needs Microsoft backend review. Gather timestamps and correlation data before the evidence rolls off

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

Share via

SQL Elastic Pools Not Responding - Timeout error / unable to access table via SQL Management Studio

1 answer

Your answer