Based on the troubleshooting you've already completed, this appears to be a Query Activity monitoring/UI issue rather than a Dedicated SQL Pool execution issue, because:
- Queries are executing successfully.
- Active requests can still be viewed through SQL queries/DMVs.
- Multiple users are experiencing the same behaviour.
- Incognito mode did not help.
- Restarting the pool did not resolve the issue.
- The SQL pool remains online and operational.
Verify whether the issue is limited to the Query Activity UI
Run the following query while a known long-running query is executing:
SELECT
r.request_id,
r.session_id,
r.status,
r.submit_time,
r.start_time,
r.total_elapsed_time,
r.command,
s.login_name
FROM sys.dm_pdw_exec_requests AS r
LEFT JOIN sys.dm_pdw_exec_sessions AS s
ON r.session_id = s.session_id
WHERE r.status NOT IN ('Completed', 'Failed', 'Cancelled')
ORDER BY r.submit_time DESC;
If the DMV returns active requests but the Query Activity pane still shows "No data found", then the SQL engine is functioning correctly and the issue is likely in the monitoring layer used by the portal.
Check the permissions
Although queries may run successfully, monitoring data can be affected by permissions.
Verify that affected users have: VIEW DATABASE STATE and appropriate Azure RBAC permissions on the Synapse workspace/resource. A useful validation is to compare behaviour between a standard user account and a workspace administrator account.
Check browser developer tools
Open F12 -> Network, refresh the Query Activity blade, and look for failed requests such as:
- 401 (authentication)
- 403 (authorization)
- 429 (throttling)
- 5xx (service-side failures)
Pay particular attention to requests made to:
-
management.azure.com
- Synapse monitoring endpoints
- Workspace monitoring APIs
If a request is failing consistently, the response details may help identify whether the issue is authentication, authorization, throttling, or a backend service problem.
Check Resource Health and Service Health
Since the issue affects multiple users and persists across browsers, review:
- Azure Resource Health for the Synapse workspace
- Azure Service Health for any Synapse Analytics incidents or regional degradation
Even when query execution is unaffected, monitoring experiences can occasionally be impacted separately from the SQL engine.
Additional checks
A few other items worth validating:
- Confirm whether the issue occurs in both Azure Portal and Synapse Studio.
- Test with a different Dedicated SQL Pool in the same subscription, if available.
- Verify whether all users are affected or only users from a specific Azure AD group/role assignment.
- Check whether recent RBAC, Conditional Access, or network policy changes were introduced around the time the issue began.
Temporary workaround
Until the Query Activity pane functions correctly, you can monitor active requests directly from the Dedicated SQL Pool DMVs:
SELECT *
FROM sys.dm_pdw_exec_requests
WHERE status NOT IN ('Completed', 'Failed', 'Cancelled')
ORDER BY submit_time DESC;
Given that active queries remain visible through DMVs and query execution is unaffected, I would focus investigation on the monitoring experience, permissions, RBAC configuration, authentication flow, or monitoring API layer rather than the Dedicated SQL Pool engine itself.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.