Getting started
SQL Server Health Monitor watches multiple SQL Server instances agentlessly – purely over a normal SQL connection, with nothing installed on the monitored servers.
Up and running in three steps
- Add a server – under Servers → New, create an instance with a name and connection string. The connection string is stored encrypted (see Backup & keys).
- Check the dashboard – the Dashboard shows fleet status, per-server health cards and active alerts. Click through to any detail page from there.
- Set up alerts – define thresholds under Settings → Alerts. Recommended: start with the default rules and refine over time (see Alerts & hysteresis).
What is collected?
CPU, memory, queries, wait statistics, blocking/deadlocks, index health, storage, tempdb,
backups and SQL Agent jobs. Collection queries run with READ UNCOMMITTED and are designed
for low overhead.
Cloud targets
| Target | Support |
|---|---|
| SQL Server on-premises | Full feature set |
| Azure SQL Database | DMVs limited, msdb queries skipped |
| Azure SQL Managed Instance | Mostly full |
| AWS RDS for SQL Server | Without msdb queries |
The engine edition is detected automatically; unsupported features are disabled.
Multilingual
The UI is available in German and English. Switch it top-right via the language picker.