26 February,2013 by Jack Vamvas
Maintaining SQL Server environments is supported by a dependable monitoring system and regular reporting of health indicators. Monitoring and reporting , although both supplying information, serve different purposes.
Monitoring focuses on immediate situations : SQL Server monitoring situations - SQL Server DBA
Reporting focuses on environmental and server wide deviations occurring in the course of daily SQL Server – Daily Health Check Script with ... - SQL Server DBA
The key to an effective monitoring framework is isolating the important\critical\fatal events. For example, creating an alert for the CPU hitting 50% is not as critical as the database is offline. I’ve worked in different SQL Server shops where there are to many monitoring alerts occurring creating extra noise for the DBA team, eventually the DBAs start missing the critical events causing extra downtime
The key to useful reporting is identifying the relevant data required to maintain the SQL Server environments. Typical areas include SQL Server security policy exceptions, database file configurations, SQL Server Error Logs. Extra Tip: Retain the reports in an archive for future reference in troubleshooting and audits.
System Reserved Partition and monitoring
SQL Server Database Status,monitoring and Restores
How to report a SQL Server performance problem
SQL Server Database Size and Free Disk Space Daily Report
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |