Applications Systems

Long-running SELECT query on NodeIPAddresses and NodeMACAddresses tables causes high SQL resource utilization in SolarWinds Platform

This article provides information about an issue where a long-running SELECT query involving the NodeIPAddresses and NodeMACAddresses tables causes high SQL resource utilization or blocking sessions in the SolarWinds database. The behavior has been observed in environments running SolarWinds Platform 2025.x, primarily affecting systems with large node inventories.

First published date

11/4/2025 10:38 PM

Last published date

11/5/2025 9:11 PM

Overview

In some environments, users may observe that a SELECT query continues to run for several hours (sometimes over a day) in SQL Server, even when no active blocking is detected. The query can appear in SQL activity captures (such as sp_WhoIsActive output or DPA Top SQL) as follows:

 

SELECT ip.NodeID, ip.IPAddress, mac.MAC
FROM NodeIPAddresses ip WITH (NOLOCK)
JOIN NodeMACAddresses mac WITH (NOLOCK) ON ip.NodeID = mac.NodeID
ORDER BY ip.NodeId

 

In affected systems, this query may:

  • Consume high CPU or I/O resources.
  • Run for extended durations (several hours or longer).
  • Cause delayed performance in other database operations.

 

This behavior has been observed even when the other background database maintenance jobs are disabled.

Product section

Server Application Monitor

Cause

The issue occurs due to an inefficient database query related to the mapping of nodes and cloud instances. The current query retrieves all node IP and MAC address information without filtering out unmonitored (ICMP-only) nodes, which can lead to unnecessary data processing and longer execution times in large environments.

Resolution

This issue has been addressed in SolarWinds Platform 2025.4 through database query optimization.

The updated logic now filters out unmonitored (ICMP-only) nodes and improves overall performance of the mapping process.

Action:

Upgrade to SolarWinds Platform 2025.4 or later to benefit from the optimized query and improved database efficiency.