This blog is part of the blog series named SQL Server Monitoring.
Purpose
To get a quick overview of the instance status.
Sources
This output here is based on the DMV sys.dm_server_memory_dumps which returns information about the dump files existing on the SQL Server, the DMV msdb.suspect_pages which returns information about suspect pages on databases reporting the file and page id that is suspect and the master.dbo.xp_readerrorlog which returns the content of the SQL Server log files where here it is only used the current file (Id 0).
Report
The report shows 3 tables where the upper one shows content of the error logs collected, the middle one shows the dump files reported on the instance, and the lower one reports about detected suspect pages on the instance.
By default it is SQL Server log records with severity level equal to 17 or above that are collected as error logs.
Model
The model for the report uses the facts [Error logs], [Instance dump files], [Instance suspect pages], and the dimension [Date].
It is the same model that are used by the Instance configuration and Resource Governor configuration reports.
Configuration
The feature accepts a SeverityLevel parameter to specify which SQL Server log records that are going to be collected as error logs.
Scheduling
The default schedule for the feature is once every hour.
Retention
The default retention for the table dbo.fhsmInstanceState is 1.825 days (5 years).
