29 Apr A Closer Look at SQL Server Health Checks
In a previous blog, we discussed how to win new business with a variety of IT assessments. In this installment, we’re going to take you deeper into one of the blogs on that list: SQL Server health checks.
If you have clients that run applications on SQL Servers, dedicated assessments can power you to help your clients better manage their networks. Server health checks can deliver critical information to identify threats and assess overall database health before a risk becomes an incident.
Three major areas are evaluated in an SQL server health assessment: settings, file, and resources.
A settings check scans for configuration concerns that do not align with best practices.
File assessments analyze how the database interacts with the file system. They determine whether adequate space is available compares the current configurations with best practices.
Resources health checks look for performance issues and confirm whether the SQL Server has adequate resources for optimal operation. These assessments are subdivided into wait health, task health, and memory health.
Wait – concerns database processing waits and delays
Task – validates that scheduled tasks and jobs are functioning properly
Memory – determines if sufficient memory is available to run the SQL Server
SQL Server assessments are based on best practices published by Microsoft and other sources. However, the health check parameters are not absolute. Occasions may arise where a best practice may need to be overlooked.
Even if you already have a Remote Monitoring & Management (RMM) system, it can’t document the SQL Server settings – valuable information to improve disaster recovery that you need in addition to the back-up. Database fragmentation and missing indices are other troubles that an RMM won’t report on. This module will help you spot these symptoms before they create problems.
Ask for a demo of Network Detective to see how it works.