Advisory Conditions

Number of records per second fetched through forwarded record pointers. This number should be as close to 0 as possible. More Information: Performance Monitor Counters for SQL Server (mssqltips.com)

Returns a count of Top SQL timeouts for Amazon AWS targets. Alert will trigger if there is a count higher than 0.

Detects whenever the server-wide max degree of parallelism (MAXDOP) server config setting changes on a server with more than one processor, by comparing the last value retrieved to the current value.

The behavior of the storage engine once VertiPaq Nonpaged Memory reaches the VertiPaq Memory Limit depends on the VertiPaq paging policy that is configured in the instance's SSAS properties. The default paging policy of 1, will allow paging to the Windows page file. This means that if the required memory to store what is needed in the VertiPaq engine exceeds the configured limit, paging will occur to the Windows page file. However, if the paging policy is changed to 0, this disables paging. If the...

The behavior of the storage engine once VertiPaq Nonpaged Memory reaches the VertiPaq Memory Limit depends on the VertiPaq paging policy that is configured in the instance's SSAS properties. The default paging policy of 1, will allow paging to the Windows page file. This means that if the required memory to store what is needed in the VertiPaq engine exceeds the configured limit, paging will occur to the Windows page file. However, if the paging policy is changed to 0, this disables paging. If the...

With the default paging policy for SSAS Tabular set to 1, paging is allowed. This means that if the memory required for the VertiPaq storage engine exceeds the configured VertiPaq memory limit, data can be paged to the Windows page file. Similarly, a setting of 2 allows utilizing a memory-mapped file. While these files may take advantage of operating system file cache, it is still less efficient than storing the data as nonpaged VertiPaq memory. Increasing the VertiPaq Memory Limit setting in your...

With the default paging policy for SSAS Tabular set to 1, paging is allowed. This means that if the memory required for the VertiPaq storage engine exceeds the configured VertiPaq memory limit, data can be paged to the Windows page file. Similarly, a setting of 2 allows utilizing a memory-mapped file. While these files may take advantage of operating system file cache, it is still less efficient than storing the data as nonpaged VertiPaq memory. Increasing the VertiPaq Memory Limit setting in your...

With the default paging policy for SSAS Tabular set to 1, paging is allowed. This means that if the memory required for the VertiPaq storage engine exceeds the configured VertiPaq memory limit, data can be paged to the Windows page file. Similarly, a setting of 2 allows utilizing a memory-mapped file. While these files may take advantage of operating system file cache, it is still less efficient than storing the data as nonpaged VertiPaq memory. Increasing the VertiPaq Memory Limit setting in your...

The IOProcess thread pool separates reads from other activities. If the I/O job queue length is consistently above 0, you may be experiencing an IO bottleneck. See the Analysis Services MOLAP Guide for SQL Server 2012 and 2014 for more information, including optimizing for NUMA.

This condition will query dbo.suspect_pages in the MSDB database, checking the number of fixed pages (event types 4, 5, and 7) per-database. This condition will fire if the number of fixed pages has increased since the last check. If this check fires then it can mean that either DBCC CHECKDB has corrected or deallocated pages, or if Enterprise Edition is in use and the database is in either an Availability Group or Mirroring session where the pages could have been fixed via Automatic Page Repair...

This condition checks the number of rows that are present in the dbo.suspect_pages table in the MSDB database, when the total count of records in the table is 900 the alert will fire. This is because the dbo.suspect_pages table can only contain a maximum of 1000 records before it fills at which point any new suspect pages that are detected will not have information logged about them.

This condition queries the dbo.suspect_pages table located in the MSDB database. If there are any pages with a status of 1, 2, or 3 then it will evaluate to True, advising that there is potential corruption in databases on the server being queried. See also: Monitor for Suspect Pages (www.dnsstuff.com)

This condition identifies where multiple Availability Replicas from the same Availability Group have their VMDKs in the same VMware Datastore. If there is an issue with the Datastore for the VMware server, this could result in an outage that nullifies the AlwaysOn Availability Group configuration within the Virtual Machines hosted on the VMware Infrastructure. See also: Always On Availability Groups & VMs - Orange Matter (solarwinds.com)

This condition identifies where multiple Availability Replicas from the same Availability Group are hosted on the same VMware/Hyper-V host. In the event of an issue with the Host server, there could be an outage that nullifies the AlwaysOn Availability Group configuration within the Virtual Machines hosted on the VMware Infrastructure. See also: Always On Availability Groups & VMs - Orange Matter (solarwinds.com)

The behavior of the storage engine once VertiPaq Nonpaged Memory reaches the VertiPaq Memory Limit depends on the VertiPaq paging policy that is configured in the instance's SSAS properties. The default paging policy of 1, will allow paging to the Windows page file. This means that if the required memory to store what is needed in the VertiPaq engine exceeds the configured limit, paging will occur to the Windows page file. However, if the paging policy is changed to 0, this disables paging. If the...

Determine if SQL Server has been patched against Meltdown/Spectre This only checks the SQL Server patch status, not the operating system or hardware This works for SQL Server 2008 through SQL Server 2017 You can use a Microsoft-provided PowerShell script to check your operating system and hardware patch status as decribed in this Microsoft KB Windows Client Guidance for IT Pros to protect against speculative execution side-channel vulnerabilities https://support.microsoft.com/en-us/help/4073119/protect...

This alert looks for the presence of the MrbMiner malware by checking for an account in sys.sql_logins. In case a system with this account is found, full network audits are recommended. More info: https://www.zdnet.com/article/new-mrbminer-malware-has-infected-thousands-of-mssql-databases/

This alert looks for the presence of the MrbMiner malware by checking for an account in sys.sql_logins (in the master database). In case a system with this account is found, full network audits are recommended. More info: https://www.zdnet.com/article/new-mrbminer-malware-has-infected-thousands-of-mssql-databases/

Alerts about high utilization for In-Memory OLTP in percentage of the limit of the service tier (at the end of the reporting interval). This includes memory used for storage of the following In-Memory OLTP objects: memory-optimized tables, indexes, and table variables. It also includes memory used for processing ALTER TABLE operations. This condition can only work when connecting to the " master " database in your Azure SQL Server. NOTE: When a database is a member of an elastic pool, resource statistics...

Alerts about Azure SQL Database throttling and deadlocks events. You can use this information to track or troubleshoot your database activity with SQL Database. This condition can only work when connecting to the " master " database in your Azure SQL Server. For more info: https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-event-log-azure-sql-database