SQL Server Dashboard
Use the Dashboard to see what one SQL Server instance does: its active tasks, their waits, and the busiest statements.
Before you begin
- You need the View SQL Server and View Dashboard permissions. Open the Dashboard from the Databases page or the database bar.
- Scops samples the instance every 5 seconds by default and keeps the samples for 15 days (see Retention). A window longer than four hours uses hourly summaries.
Show one database
In the database bar, click All databases next to the name of the instance.
Select a database. If the instance has more than 12 databases, type in Find a database.
The page then shows only that database. Findings shows its findings and those of the instance. The other pages of the instance keep your choice. To show all databases again, select All databases.
Read the values at the top
A value has a color only when it needs attention. Hover over it for the detail. A dash with not read means that Scops could not read the value.
| Value | What it shows | Click to open |
|---|---|---|
| Active requests | The requests that are part of the load now. | Live Activity |
| Blocked | The requests that wait on a lock of another session, and the session that blocks them. Amber when the longest wait is 1 minute or more, red from 5 minutes. | The Blocking tab of the Instance window |
| CPU | The CPU that SQL Server uses, and under it the CPU of other processes. Amber from 80% in total, red from 90%. Amber also when tasks wait for a processor. | The CPU tab |
| Memory | The memory that SQL Server uses, of the memory that it aims for. Amber when queries wait for a memory grant, or when memory is low. | The Memory tab |
| Log | The fullest transaction log of the online databases, and its database. Amber from 80%, red from 90%. Scops reads it every 10 minutes. | The Transaction Logs tab |
| Tempdb | How full tempdb is, and its size. Amber from 80%, red from 90%. | The Tempdb tab |
| Always On | Only when the instance has availability groups. The worst synchronization health: Healthy, Partially healthy (amber) or Not healthy (red). Red also when a replica is disconnected. | The Always On tab of Health Check |
When you show one database, Log is the log of that database. CPU, Memory, Tempdb and Always On stay values of the instance: they show instance next to their label.
Look at a value over time
Click Blocked, CPU, Memory, Log or Tempdb. The Instance window opens on the tab of that value.
Select the period: 1H, 1D, 1W or 1M. Transaction Logs has no 1H.
To open the full page, click the button at the bottom, for example Open Metrics.
| Tab | Charts | Below the charts | Button |
|---|---|---|---|
| Blocking | Lock waits | Head blockers: the sessions at the head of a chain now, at most 8. | Open Blocking |
| CPU | CPU usage, Runnable tasks | Open Metrics | |
| Memory | Server memory, Page life expectancy | Open Metrics | |
| Transaction Logs | Log space used of one database | The log of each online database. Click a row to show its history. | Open Health Check |
| Tempdb | Tempdb space used, by type | Sessions using tempdb now, at most 8. | Open Metrics |
In a table, click a query hash to open the statement details.
Open the findings
Click Findings. The number shows the open warning and critical findings. It is red when one is critical, and amber for warnings only. 0 means that no finding is open, and the button does not open. A dash means that Radar Engine does not watch this instance.
In the Findings panel, click a row to read the finding.
Alert log, in the footer of the panel, opens all alerts and findings of the instance on Incidents, in a new tab.
Choose the time window
| Button | Window |
|---|---|
| Live | The last hour. The page refreshes every 15 seconds. |
| 1D, 1W, 1M | 24 hours, 7 days or 30 days, in hourly, 4-hour or daily bars. The window moves to the newest data every 5 minutes. |
| Calendar button | Any range of 92 days or less. Select From and to, then click Apply. |
To move the window, drag the box on the strip under the chart. To open one bar of a 1D, 1W or 1M window, click the bar. All times use the clock of the instance.
Read the Activity chart
The chart stacks the average active tasks by wait category. A task on a processor is CPU. A task that is ready to run and waits for a processor is CPU queue.
To change the split, select Wait Category, Wait Type, Database, Application, Login or Host in the chart header. A choice that does not fit is under More. Host is available only for a window of four hours or less.
| On the chart | Meaning |
|---|---|
| The red dashed line | The number of cores. When CPU and CPU queue reach it, the instance is short of CPU. |
| A line with a shade under it | The usual activity at this time of the day, learned from the last 28 days. The readout shows it as Usual. It does not show while a Breakdown row filters the page. |
| A gap | Scops could not sample. A gap is not zero. |
| A status shape | A Radar finding opened there. Point to it to see the finding. Click it to open the finding. |
Select a range
Drag across the chart. A chip in the chart header shows the range.
To move the start or the end, drag the edge of the range.
To clear the range, click the chip or Live.
The Breakdown and the Statements then show only that range. Without a range, they show the full window, or the last 5 minutes in Live.
Filter by wait, database, login, application or host
In Breakdown, select Wait, Database, Login, Application or Host.
Click a row. The chart, the Breakdown and the Statements show only its activity. A chip in the chart header names it.
To show all rows again, click the row again or the chip.
When you show one database, the Breakdown has no Database list.
Find the busiest statements
The Statements tab lists the statements of the range, the busiest first. Each statement shows as its query hash.
| Column | What it shows |
|---|---|
| Statement | The query hash. Work without a query hash shows its command. |
| Activity | The average active tasks, in a bar split by wait category. |
| Statement Text | The object of the statement, then the start of its text. encrypted means that the server gives no text for the module. |
| Top Wait | The wait type with the most tasks, or On CPU. |
| Sessions | The sessions that ran it. Not shown for a window longer than four hours. |
| Database | The database where it ran most. +2 means that it also ran in 2 more databases. |
| Tag | Meaning |
|---|---|
| 2 plans | The statement ran with more than one plan. |
| DOP 8 | A parallel run, and the most tasks that it used. |
The tags do not show for a window longer than four hours.
Open or find a statement
- Click a row. Its statement details open for the same range.
- Or type a query hash in the box next to the tab, with or without
0x, and press Enter. - To find statements by a piece of their text, or by a table or object, type it in the box. The list shows only the statements of the window that contain it. Press Esc to clear the box.
Related
Updated November 22, 2026