Database Management

Cluster nodes are not displayed correctly in SQL Sentry's Hyper-V topology

SQL Sentry's automatic Hyper-V discovery can lead to an incorrect representation of the Hyper-V topology.

First published date

1/5/2026 9:54 PM

Last published date

1/9/2026 8:26 PM

Overview

The issue is that cluster nodes from the WSFC.Cluster and WSFC.Node tables are incorrectly shown in the Hyper-V section of the Navigator Pane, even when Hyper-V is not enabled on those clusters.

Hyper-V

Product section

SQL Sentry (SQLS)

Cause

The root cause is SQL Sentry’s automatic Hyper-V discovery process, which includes all clusters and nodes from the WSFC.Cluster and WSFC.Node tables in the Hyper-V topology view, regardless of their actual Hyper-V status. 

Resolution

 

  • Temporary Removal: Deleting the nodes from the client or the WSFC.Node table will only temporarily remove them; they will reappear after the next data collection.
  • No Permanent Fix: As of now, there is no supported way to fully disable Hyper-V discovery or permanently remove these entries.
  • Engineering Status: A feature request is submitted to add the ability to disable Hyper-V discovery and allow permanent removal of these entries.
  • Best Practice: If you are monitoring clusters that do not use Hyper-V, be aware that these may still appear in the Hyper-V topology due to the current discovery logic. Monitor individual Windows machines that are part of a Windows Cluster, as SQL Sentry is not cluster-aware for non-Hyper-V clusters.