Problem Statement

Under Queries, the current Active Queries tab appears to show historical rows from previous collections as well (i.e., not strictly what is active right now). This makes it harder to quickly see the currently running queries at a glance when troubleshooting something live.

Related: refreshing to see “right now” activity feels slow. My impression is that clicking Refresh Tab refreshes all pages/tabs under the main section (not just the currently selected sub-tab), though I’m not 100% sure—just basing that on how long the refresh takes.

Proposed Solution

Add a separate tab under Queries dedicated to Currently Active Queries (only what is active at the moment of refresh), independent of historical collections.

One idea would be for this tab to display results from sp_WhoIsActive (or an equivalent “current activity” query) directly, and allow that specific tab to be refreshed on demand without triggering a refresh of other tabs/sections.

If feasible, it would also be nice if Refresh Tab truly refreshed only the selected sub-tab (or provide a separate “Refresh This View Only” action).

Use Case

When investigating an ongoing performance incident (blocking, long-running query, sudden CPU spike), I’d go to Queries → Currently Active Queries, hit refresh repeatedly, and immediately see only the sessions/queries executing right now—similar to running sp_WhoIsActive in SSMS.

Alternatives Considered

• Manually running sp_WhoIsActive in SSMS as a workaround.
• Filtering/sorting the existing Active Queries view to approximate “current” activity, but it’s still based on collected history rather than a true live snapshot (and requires extra steps).

Additional Context

• Is this related to a specific SQL Server version? Not specifically (I’m on SQL Server 2019 CU32, but I think this is generally useful across supported versions).
• Would this require schema changes? Ideally no, if it’s a direct live query/snapshot view rather than persisted collection data (but I’m not sure how the dashboard is structured internally).
• How frequently would you use this feature? Quite often during live troubleshooting—potentially multiple times per day in busy environments.

Scope

Please indicate which component(s) this affects:

• Full Dashboard
• Lite
• SQL collection scripts
• Installer
• Documentation

IMPORTANT: If you're going to contribute code, please read the contributing guide first.