Version & Patch
Page Description
This page shows version and update information for all monitored SQL Server instances, including the installed build, applied patch level, release date of the detected version, and support status. Its purpose is to provide a quick view of compliance against recommended versions and help identify servers that need review, maintenance, or an upgrade.
The page combines an aggregated view with a detailed one. The aggregated view shows how many instances are running each SQL Server version, which is useful for spotting technology sprawl or environments that have not yet been standardized. The detailed view goes down to server level so you can verify whether the instance is still supported, whether its build is current, and whether there is a pending update that should be scheduled.
It also helps prioritize operational and security risk. An instance that is out of support, missing a security update, or running an outdated build can be exposed to known issues, support limitations, and more complex maintenance work. For that reason, this page is especially useful during periodic compliance reviews, hardening plans, and patching preparation windows.
Variables
There are no selectable variables defined in the top bar of this dashboard.
Version Distribution
This section provides a consolidated view of the SQL Server versions present in the monitored environment. It lets you quickly see whether the platform is standardized or whether multiple engine generations coexist, which matters when planning upgrades, validating compatibility, and reducing operational complexity.
SQL Versions
- Description: Shows the number of instances using each SQL Server version detected on the page. It helps identify clusters of older versions, heterogeneous deployments, and the potential workload associated with future upgrade campaigns.
- Type of panel: barchart
- Units: number of instances
Thresholds:
| Value | Color | Description |
|---|---|---|
| Between 0 and 80 | Displayed count without a high-concentration marker. | |
| > 80 | Very high concentration of instances on the same version. |
Practical recommendation: Microsoft recommends keeping instances on supported releases and, for SQL Server 2017 and later, installing the latest CU or at least one released within the last year. If you see many instances on older or unsupported versions, group them into a phased upgrade plan.
Detailed Update Status
This section shows the per-server detail of version, support, and update status. It brings together the instance name, installed build, support end date, current release date, and functional build status so you can decide which servers are current, which ones need review, and which ones require immediate action.
For an instance to appear as updated, the installed build must meet the panel's expected servicing criteria. For servers still within support, the expected level is the latest CU with a maximum age of 2 months. For servers in extended support, the expected level is the latest SU with a maximum age of 2 weeks. This distinction helps interpret each instance correctly according to its lifecycle phase.
Detailed Versions
- Description: Shows per-server detail for version, build, support, and update status. It helps identify supported and unsupported instances, detect available updates, and distinguish between builds that are current and builds that need intervention.
- Type of panel: table
Value-based colors:
| Column | Value | Color | Description |
|---|---|---|---|
| Supported | Supported | The instance is still within the support lifecycle. | |
| Not Supported | The instance is outside regular support. | ||
| Build Status | Updated | The build meets the expected servicing criteria. | |
| Pending Security Update | A security update is still missing. | ||
| Available Update | An update is available for the current build. | ||
| Available Update - Bugged AG Version | An update is available and AG impact should be reviewed. | ||
| Pending CU and SU | Both cumulative and security updates are pending. | ||
| Available Update - Security Zero Day | An update exists for a critical vulnerability scenario. | ||
| Pending Extra Paid Security Update - Out of Support | ESU is required and the instance is already out of support. | ||
| Pending Extra Paid Security Update | A paid extended security update is required. |
Practical recommendation: Prioritize rows marked Not Supported, Pending Security Update, and Pending CU and SU first. Microsoft narrows servicing options once a version enters extended support and, once it is out of support, the sustainable path is upgrade or migration; ESUs should be treated only as a temporary bridge while that plan is executed.