Use the Is a Cluster Node health check in Mini DBA to review SQL Server configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for high availability, topology, or feature state that affects operations and recovery planning.
The check turns an operational best practice into a repeatable Mini DBA review item so teams do not rely on memory or occasional manual audits.
Confirm the intended topology, replica health, failover design, and operational runbook. Correct stale slots, closed PDBs, lagging replicas, or undocumented feature use before relying on the environment for recovery.
Keep a short note explaining why the check failed, what was changed, who owns the follow-up, and whether an exception was approved.
Prioritize it by blast radius. Fix it quickly when it affects a production workload, a shared server, or a customer-facing service; otherwise place it in the normal improvement backlog with an owner.
Prevent repeat failures by assigning an owner, documenting the expected configuration, and reviewing the check after upgrades, migrations, or major application releases.
Add this page to the operational runbook for SQL Server environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.