SQL Server Health Check
A fixed-scope assessment of your SQL Server environment — backups, jobs, performance, security, and HA/DR — delivered as a prioritized written report.
Know what's working, what's broken, and what needs attention before it becomes a problem.
Most SQL Server problems don't announce themselves. Backups that appear to be running but have never been tested. Index fragmentation that's quietly degrading query performance. SQL Agent jobs failing silently at 2 AM. Security configurations left at install defaults.
A SQL Server health check is a structured review of your environment — not a sales pitch for a larger engagement. The goal is a clear, honest picture of where things stand, with findings prioritized by risk so you know what to address first.
This is a fixed-scope service. One instance, one deliverable. No open-ended retainer required.
What's Included
- Backup strategy and recent backup verification
- SQL Agent job status and failure history
- Database mail and alerting configuration
- Performance baselines: wait stats, missing indexes, top queries by CPU and I/O
- Index health: fragmentation, unused indexes, duplicate indexes
- Security review: logins, server roles, linked servers, sa account, Windows vs. SQL auth
- Configuration review: max memory, MAXDOP, cost threshold, TempDB file count
- HA/DR readiness: AG synchronization state, backup on secondaries, failover history
- Database consistency checks (DBCC CHECKDB status and history)
- Disk space and data file growth settings
Deliverable: Written report with findings organized by priority — critical, warning, and informational.
This service is a fit when:
You inherited a SQL Server environment
New to a role and not sure what the previous DBA left behind. A health check provides a documented starting point before you make changes.
You're preparing for an audit or compliance review
Security configuration, access control, and backup verification are common audit targets. Having a pre-audit review surfaces problems before auditors do.
Performance has degraded and you're not sure why
A baseline review of wait stats, top queries, and index health often identifies the leading contributors without requiring days of investigation.
You're planning an upgrade or migration
Before moving from SQL Server 2016 to 2022, or on-prem to Azure, it's worth knowing the current state of the environment you're migrating from.
You have no dedicated DBA
Many organizations run SQL Server with no in-house DBA support. A periodic health check provides outside eyes on an environment that rarely gets reviewed.
You want to validate your current setup
If you've managed SQL Server in-house for years, a health check confirms what's working well and flags gaps you may not have considered.
A written report you can act on.
The output is a structured written report organized by risk level. Critical findings come first — things that represent active data loss risk or security exposure. Warning findings are items that need attention but aren't immediately dangerous. Informational findings document configuration state and performance observations.
Each finding includes what was observed, why it matters, and a recommended next step. The report is written to be readable by both technical and non-technical stakeholders.
Related checklists for reference:
How it works.
Remote access to the SQL Server instance is required — either via VPN or a remote session. Read access to system DMVs, SQL Agent, and configuration views is sufficient; no schema changes or writes are required.
The review takes approximately two to four hours of elapsed time depending on instance size and complexity. The written report is delivered within one to two business days of the review session.
To start, reach out by email or through any of the profiles below. A brief discovery call is typically the first step to confirm scope and access requirements.
More SQL Server resources
SQL Server Consulting Services · SQL Server Health Check Checklist · AG Setup Checklist · Migration Planning Guide · SQL Server Security and Compliance · Database Design Services
Frequently Asked Questions
What versions of SQL Server does this cover?
SQL Server 2012 through 2022, on-premises and cloud-hosted (Azure SQL VM, AWS EC2). Azure SQL Database and RDS can be reviewed with adjusted scope given platform-level restrictions on certain DMVs.
Do you need write access to run the health check?
No. Read access to system DMVs, SQL Agent tables, and configuration views is sufficient. No schema changes, no writes to user databases.
Can this be done without an Always On Availability Group?
Yes. The HA/DR section is simply scoped to whatever is in place — standalone instance, mirroring, log shipping, or AG. If there's nothing in place, that's noted as a finding.
Who is Michael Paycer?
Michael Paycer is a SQL Server DBA and Developer based in Saint Cloud, Minnesota with 20+ years of experience in SQL Server administration, development, performance tuning, reporting, ETL, HA/DR, and database design.
How can I get started?
Email michael.paycer@gmail.com or reach out via LinkedIn or Upwork. A short discovery call is typically the first step.