SQL Server Version & Patch Overview
UID:
sql_server_version_patch_overviewVersion: 1.3.1 Panels: 4 Datasource: MSSQL
Purpose
This dashboard shows version and update information for all monitored SQL Server instances, including:
- Build number installed
- Patch level (CU, SP, SU)
- Release date of the current version
- Support status from Microsoft
- Update status and recommendations
This panel helps track compliance with recommended updates and identify servers that require maintenance or upgrades.
Variables
This dashboard does not use variables. It shows information for all monitored instances.
Color Codes
| Color | Code | Meaning |
|---|---|---|
| Green | #00db88 | Correct - Updated |
| Magenta | #ad21d8e8 | To Check - Update available |
| Red | #F2495C | Wrong - Urgent action required |
Panels
SQL Versions
SQL Versions barchart
Number of instances using each SQL Server version.
Interpretation
This chart allows you to quickly visualize the distribution of SQL Server versions in your infrastructure. It is useful for:
- Identifying obsolete versions
- Planning migrations
- Evaluating environment homogeneity
Detailed Versions
Detailed Versions table
Detailed table with complete version information per server.
Table columns:
| Column | Description |
|---|---|
| Server Name | Server/instance name |
| Server Build | Current installed build |
| Full Name | Full version name |
| Current Release Date | Release date of current version |
| Max Build | Most recent available build |
| Support End Date | End of support date |
| Supported | Support status (Supported/Not Supported) |
| Build Status | Update status |
Build Status state mapping:
| Status | Color | Meaning |
|---|---|---|
| Updated | Green | Version is up to date |
| Pending Security Update | Magenta | Pending security update |
| Available Update | Magenta | CU update available |
| Available Update - Bugged AG Version | Magenta | Version with known AG bug |
| Pending CU and SU | Magenta | CU and SU pending |
Supported state mapping:
| Status | Color | Meaning |
|---|---|---|
| Supported | Green | Within support period |
| Not Supported | Magenta | Outside Microsoft support |
Update Criteria
To achieve the "Updated" (green) status, the following criteria must be met:
During regular support period:
- Have the latest CU (Cumulative Update) installed with a maximum age of 2 months
During extended support period:
- Have the latest SU (Security Update) installed with a maximum age of 2 weeks
Interpretation Guide
Update Priorities
| Build Status | Priority | Action |
|---|---|---|
| Updated | - | No action required |
| Pending Security Update | High | Plan immediate update |
| Available Update - Bugged AG Version | High | Update to fix AG bug |
| Available Update | Medium | Plan update |
| Pending CU and SU | Medium | Plan maintenance window |
SQL Server Version Lifecycle
| Phase | Available Updates | Recommendation |
|---|---|---|
| Mainstream support | CUs + SUs | Apply CUs every 2-3 months |
| Extended support | SUs only | Apply SUs immediately |
| Out of support | None | Migrate to supported version |
Out of Support
Servers marked as "Not Supported" do not receive security updates from Microsoft and represent a significant security risk. Migration to a supported version should be planned.
Stored Procedures Used
| Procedure | Description |
|---|---|
[Home].[spCheckInstanceUpdatedExtended] | Returns detailed version and update status information |
Tables/Views Used
| Object | Description |
|---|---|
[dbo].[hc_instance_configuration] | Instance configuration with version information |
Recommendations
Patching Best Practices
- Maintain an update schedule: Review available updates monthly
- Prioritize security updates: SUs should be applied as soon as possible
- Test in development environments: Before applying in production
- Document versions: Maintain a record of update history
Migration Planning
For servers without support or with very old versions:
- Evaluate application requirements
- Identify compatibility changes
- Plan migration to LTS (Long-Term Support) version
- Consider SQL Server 2019 or 2022 as the target
