SQL Server Health Checks run server-level checks and show findings that can affect reliability, performance, configuration, and operations.
Use health checks to detect configuration risks, maintenance gaps, resource concerns, and operational issues that are easy to miss during incident response.
Health checks are most useful when findings are prioritized by risk and context. Start with issues that affect availability, backups, corruption risk, capacity, security exposure, or recurring performance pain. Lower-priority configuration warnings may still matter, but they should not distract from urgent operational risk.
For service review work, export or summarize health check findings with supporting evidence from queries, waits, files, Agent jobs, and alerts. A good remediation plan should include the finding, affected server, business impact, recommended action, owner, and target date.
No. Some are informational or best-practice warnings. Review severity and business context before acting.
Use your normal change process. Health checks provide evidence and recommendations, but production changes should be reviewed and tested.
Some checks read SQL Server metadata, Agent jobs, error logs, server properties, or database-level details that require additional permissions.
The following Mini DBA SQL Server health check detail pages explain the purpose of each check and the actions to take when a check fails.
| Health check | Category | Detail |
|---|---|---|
| Full Recovery Log Backups | Backup | Open detail |
| Max Server Memory Recommended | Configuration | Open detail |
| Suspect Pages | Corruption | Open detail |
| Slow reads | FileConfiguration | Open detail |
| Slow writes | FileConfiguration | Open detail |
| System databases on C drive | FileConfiguration | Open detail |
| TempDb data files uneven | FileConfiguration | Open detail |
| TempDb files on C drive | FileConfiguration | Open detail |
| TempDb only has 1 data file | FileConfiguration | Open detail |
| TempDb percent growth | FileConfiguration | Open detail |
| Is a Cluster Node | Informational | Open detail |
| Server level triggers | Informational | Open detail |
| Startup procedures | Informational | Open detail |
| User tables in master database | Informational | Open detail |
| Actionless sys alerts | Monitoring | Open detail |
| No Sql Agent operator enabled | Monitoring | Open detail |
| Plan Guides In Use | Performance | Open detail |
| Potential OS Memory Swapping | Performance | Open detail |
| Resource Governor Enabled | Performance | Open detail |
| Query hints - join | QueryPlans | Open detail |
| Query hints - sort order | QueryPlans | Open detail |
| SQL Server Version Support | Reliability | Open detail |
| Database Owners | Security | Open detail |
| Non SA owned jobs | Security | Open detail |
| Orphaned Database Users | Security | Open detail |
| Security admins enabled | Security | Open detail |
| SQL Login Password Policy | Security | Open detail |
| SQL Server Audit Enabled | Security | Open detail |
| User Endpoints Started | Security | Open detail |
| xp_cmdshell | Security | Open detail |