Observability

Applying Microsoft SQL Server update to address security vulnerabilities

This article provides information about best practices for applying Microsoft SQL Server updates to address security vulnerabilities in environments running SolarWinds Platform.

First published date

9/9/2025 3:31 PM

Last published date

9/9/2025 3:31 PM

Overview

The SolarWinds Platform relies on a Microsoft SQL Server instance to host its databases. Microsoft regularly releases security patches to address vulnerabilities in SQL Server. These updates are considered third-party maintenance and are not supported directly by SolarWinds. However, SolarWinds recommends keeping SQL Server fully patched to maintain a secure and stable environment.

This article provides guidance on:

  • Verifying your current SQL Server version
  • Locating and downloading the latest updates from Microsoft
  • Safely applying updates with minimal impact to SolarWinds operations

While no specific error messages are tied to unpatched SQL vulnerabilities, failure to apply updates may expose your environment to known risks as outlined in Microsoft Security Bulletins.

Product section

Hybrid Cloud Observability

Cause

Vulnerabilities in Microsoft SQL Server that require patching, as identified and remediated by Microsoft security updates. These are not caused by SolarWinds software but by external factors in the SQL Server ecosystem.

Resolution

How to verify the Microsoft SQL Version running:

https://learn.microsoft.com/en-us/troubleshoot/sql/releases/find-my-sql-version 

List of updates available for the supported Microsoft SQL Version:

https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Before applying a Microsoft SQL Server update, we recommend following the steps:

Important Notice:

 

  1. Stop all SolarWinds services on all SolarWinds servers and disable High Availability if deployed.
  2. Install the Microsoft SQL update. 
  3. If a reboot is required, follow the recommended reboot sequence
  4. Restart SolarWinds services and re-enable HA if applicable.
  5. Verify SolarWinds functionality post-update, such as checking database connectivity and monitoring dashboards.