Memory dump Alert occurs when a memory dump has occured. Memory dumps should never occur, and is a critical alert. To query the Performance Store database for the last 10 memory dumps: 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 […]

Wrong default schema name When creating a new login, the default schema owner of the login can by mistake be set to the actual name of the login, e.g. login DEV\TestUser1 will have the default schema name DEV\TestUser1, which is not recommended. If the DEV\TestUser1 executes the following statement “create table table1 (id int)”, the […]

Non-existing servers in backup time whitelist One or more servers exists in the database backup time whitelist table dbo.database_backup_time_whitelist, but the servers do not exist. To query the Performance Store database for non-existing servers in the backup time whitelist, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this […]

Non-existing databases in backup time whitelist One or more databases exists in the backup time whitelist table dbo.database_backup_time_whitelist, but the databases do not exist. To query the Performance Store database for non-existing databases in the backup time whitelist, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this alert, […]

Replicas with non-identical service accounts SQL Servers that are replicas in Availability Groups should have identical SQL Server service accounts. If the SQL Server service accounts are not identical, it is not possible to set up SPNs correctly to linked servers pointing to the Availability Group listener. To query the Performance Store database for replicas […]

Server security differences An alert will be thrown, if two SQL Servers are a failover pair, and there are differences in the securables between the two servers. To query the Performance Store database for differences in securables between two servers, use: Securables can be synchronized between servers by executing the “create_statement” from the dbo.v_securables view. […]

High row count change If a production database is having a table with more than 1 million rows and an increase in the number of rows of more than 20 %, this alert is raised. To query the Performance Store database for tables with high row count changes, use: The alert will be visible on […]

Non-existing servers in licensing whitelist If a server has been included in the dbo.errors_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 errors collection, use: The alert will be visible on the Latest […]

Log drive with incorrect cluster size Alert will be raised for log drives with a cluster size different from either 8K or 64K. To query the Performance Store database for log drives with incorrect cluster sizes, use: The alert will be visible on the Latest stats dashboard. To exclude specific servers from this alert, see how […]

Transaction log full Alert will be thrown if the transaction log is full. To query the Performance Store database for databases where the transaction log is full, 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.