Server configuration differences An alert will be thrown, if two SQL Servers are a failover pair, and there are differences in the configuration between the two servers. It is a common problem that the server settings are different between two failover nodes. To query the Performance Store database for configuration differences between two servers, use: […]

Server security differences An alert will be thrown, if two SQL Servers are a failover pair, and there are differences in the security between the two servers. It is a common problem that logins differs between two failover nodes. To query the Performance Store database for security differences between two servers, use: Logins can be […]

SA user with default name It is advised to rename the sa user, so the default name is not “sa”. To query the Performance Store database for servers where the SA user has not been renamed, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this alert, see how […]

SA user not disabled It is advised to disable the sa user so it is not possible to login with the sa user. To query the Performance Store database for servers where the SA user has not been disabled, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this […]

Primary- and secondary availability groups on same server To query the Performance Store database for servers with both primary- and secondary availability groups placed on the same server, use: Due to SQL Server licensing, servers must only contain availability groups that are either either primary or secondary. For at description of the different availability_group_info values, […]

Primary and secondary placed on same host In case of a host- or connection failure, it is not advised to have both the primary- and secondary server in an availability group on the same physical host. To query the Performance Store database for servers where the primary and secondary are placed on the same host, […]

Plan cache can be optimized If the SQL Server plan cache consists of more than 60 percent single-use plans, it is advised to enable the “Optimize for adhoc” setting. If this is the case, Performance Store will throw an alert. To query the Performance Store database for servers where the plan cache is filled with […]

Non-healthy database availability group state To query the Performance Store database for databases with a non-healthy availability group state, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this alert, see how to use the dbo.team_alert_exclude table in Alerting.

Non-existing servers in licensing whitelist If a server has been included in the dbo.licensing_whitelist table, but does not exist anymore, this alert will be thrown. To query the Performance Store database for servers that do not exist, but are marked to be excluded from the licensing functionality, use: The alert will be visible on the Latest […]

Non-existing servers in extended audit include If a server has been included in the dbo.audit_extended_include table, but does not exist anymore, this alert will be thrown. To query the Performance Store database for servers that do not exist, but are marked to be included in the extended audit functionality, use: The alert will be visible […]