SQL Server Health Check21-12-2018 0 Comment(s)
Why do we need SQL Server Health Check?
Here we are going to highlight two crucial point capacity planning and reaction time. Now let’s dig deeper and say a few words about each of them.
It’s crucial to know the capacity of our server and their limits such as Memory, storage space, I/O capacity and others. It’s important to check all these components and be ready to react in advance to the approaching threat. If we have proper automatic SQL Server health check we’ll be able to foresee the coming disaster and take necessary measures.
Here is the second point reaction time. Reaction time as important as capacity planning. If we tune all alerting and notification of our automatic SQL Server health check correctly, we’ll able to prevent server crash. The good thing of the automatic health check is that based on the statistics we detect threats before they can damage our server.
Automatic SQL Server Health Check – Key Points
Monitoring your SQL server from a different server. It will tell you if something goes wrong and your server goes down. If you use automatic health check on the same computer or server where SQL Server is installed, then probably, if the server is down, or if something wrong with you computer monitoring process will fail too. In such case, you will not receive any notification.
Create a separate database to store monitoring information. Automatic SQL Server health check needs space to store and analyze the data. It’s known that some metrics are gathered once a day while other are collecting every 5-10 minutes. Also, you need to consider how long it is necessary to keep historical data. It is recommended to store them a few months.
Testing from time to time your health check queries and scripts. Since your SQL Server health check runs automatically it’s crucial to be sure that everything works correctly.
Start from the small set of alerts. From the very beginning, it’s recommended to start from a few alerts and expand gradually.
No Comments to Show