Repository navigation
[QUESTION] Why "Top Procedures by Duration" is empty ? #1833
Description
Activity
- added a commit that references this issue
on Jul 30, 2026 There is a real bug behind half of this, and I need two settings from you to confirm the other half.
In your server entry (Manage Servers > Edit): is the Database field filled in with your actual database, or blank? And is "Read-only intent" unchecked? On Azure SQL DB a blank Database field lands the connection in master, and it turns out two collectors - procedures and Query Store - were the only ones that never switched into your actual database from there. They collected nothing from master and logged success doing it.
The procedures side is fixed for the next release. The Query Store side needs a bigger rework on Azure - it never collected there even with the Database field set correctly - and is now tracked in #1836. So: Top Procedures should populate for you after the next release (or tonight's nightly) provided your database actually executes stored procedures - if your app runs ad-hoc or ORM queries only, that grid is legitimately empty and Top Queries is the one to watch. Query Store lands with #1836.
Closing the loop on the second half: the Query Store rework (#1836) is now fixed on dev too. On Azure SQL DB the collector runs per database like everything else, gates on Query Store being enabled and writable in each, and collects the full payload - the broken cross-database probe that silently returned nothing is gone entirely. Both halves of what you reported ship in the next release; tonight's nightly carries both if you want to see data sooner. With the Database field set per the earlier questions, Top Procedures and Query Store by duration should both populate.
Manage Servers > Edit: the Database is blank
"Read-only intent" unchecked
Utility DB: someDBI work with Azure SQL db
That confirms it completely. A blank Database field on Azure SQL DB landed the connection in master, and procedures and Query Store were the two collectors that never escaped master from there. Both halves are fixed: procedures switches into each database now, and Query Store collects per database on Azure with the broken cross-database probe gone entirely. Tonight's nightly carries both, and the next regular release will too. You don't need to change anything in your server entry, the fixed collectors handle the blank Database field correctly.
Closing this as fixed. If Top Procedures or Query Store are still empty for you after updating, comment here and it reopens.
- added a commit that references this issue
on Jul 31, 2026
Which component is your question about?
Lite
Performance Monitor Version
3.2.0, 3.3.0
Is your question about how it works, or the results?
How the tool works
What's your question?
I see nothing in the "Top Procedures by duration", "Query Store by duration" but it is very interesting info
Additional Context
No response