Dedictaed SQL Pool Query Activity is not being displayed

Madhukar Muddasani 10 Reputation points
2026-10-15T18:21:16.78+00:00

SQL Pool Query activity is not displayed in Azure Portal.I am not seeing any query activities or historical.

Azure Portal --Dedicated SQL Pool --- Monitoring--- Query Activity

I am getting the message ,There is a Temporary problem loading your query activities. Please try again later.

I first noticed the message this morning. All other Azure services are running without any issue.

Thanks

Azure Synapse Analytics
Azure Synapse Analytics

An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-15T18:21:31.59+00:00

    The Azure portal Query activity view has known limitations and can also fail due to a platform-side issue.

    Key facts for this scenario:

    1. The Query activity tab in Azure portal cannot show historical executions.
    2. The pool must be resumed for the Query activity tab to show queries.
    3. The portal view does not display some statements such as DECLARE, SET, or batch details.
    4. DMV data is limited to the last 10,000 executed queries and is cleared after pause, resume, or scale operations.
    5. For exact query history, diagnostics must be enabled to export data to a destination such as Log Analytics.
    6. There has also been a reported platform bug affecting query details/insights in portal experiences, where the available mitigation was to collect the needed data directly from Query Store on the database.

    Recommended path:

    1. Verify the dedicated SQL pool is running/resumed.
    2. If the portal still shows “There is a Temporary problem loading your query activities”, treat the portal blade as unreliable for now and use an alternate monitoring path:
      • In Synapse Studio: go to Monitor hub.
      • For SQL requests: Activities > SQL requests.
      • Select the correct Pool filter to see running or completed SQL requests for that pool.
    3. For programmatic troubleshooting, query the dedicated SQL pool DMVs.
    4. If historical query tracking is required, enable diagnostic logging to export logs to Azure Monitor / Log Analytics. Expect about 10–15 minutes log latency.
    5. If Query Store is enabled, use Query Store to investigate query history and performance differences.

    If the issue started suddenly this morning and other services are healthy, that aligns with a possible portal-side/platform issue rather than a workload problem in the pool itself.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.