Contoso Group (sample data) · 2 servers checked on 2026-10-23 14:40
| Priority | Evidence | If it is not fixed |
|---|---|---|
| High | Transaction log backups are being thrown away3 occurrences, all servers | These databases can only be restored to their last full backup, not to a recent moment, and the log can grow without limit. |
| High | Backup jobs that fail regularly2 occurrences, 1 server | A backup that fails quietly leaves less protection than anyone thinks. |
| Medium | Long gaps between backupsall servers | After a failure, up to this much recent work could be lost. |
| Medium | Databases never checked for corruptionall servers | Corruption found late may already be in every backup. |
Plus 3 low-priority notes in this area.
| Priority | Evidence | If it is not fixed |
|---|---|---|
| Medium | Nobody is warned when SQL Server reports a serious error4 occurrences, all servers | Serious problems can go unnoticed until users complain. |
| Medium | Scheduled jobs that fail without telling anyoneall servers | Failures can go unnoticed for days. |
| Medium | Many accounts with full administrator rightsall servers | Every such account can read, change or delete everything. |
| Medium | Database users that could map to the wrong login after a restoreall servers | Someone could silently get another person’s access. |
| Medium | Permissions granted to every user of a database (the public role)all servers | Everyone with access to the database gets them. |
| Medium | Weak or expired encryption keys and certificatesall servers | Encrypted data may not be as protected as assumed. |
| Medium | SQL logins that ignore the password policyall servers | Their passwords never expire and can be weak. |
| Medium | Optional server features switched on that widen the attack surfaceall servers | Each one is another way in if the server is attacked. |
| Medium | Linked servers that sign in with a stored or powerful loginall servers | A weak link to another server can expose both servers. |
| Medium | Database text-comparison settings differ from the server1 server | Queries that join to temporary data can fail. |
| Medium | Accounts with very powerful permissions in databases1 server | Mistakes or misuse by those accounts have a large effect. |
| Medium | Scheduled jobs that often fail1 server | They need attention before they stop working altogether. |
| Medium | Scheduled jobs that failed this week1 server | Work they should be doing is not happening. |
| Medium | Database Mail is reporting errors1 server | Alert and job emails may not be arriving. |
| Medium | Database settings that bypass normal security checks1 server | They let code in one database act with the rights of another. |
Plus 36 low-priority notes in this area.
| Priority | Evidence | If it is not fixed |
|---|---|---|
| Medium | Cluster could split in two with no tie-breakerall servers | If the network between the servers is cut, neither side may know it should stay up. |
| Medium | Repeated connection time-outs between servers in the group1 server | The standby copies can fall behind or disconnect. |
Plus 2 low-priority notes in this area.
| Priority | Evidence | If it is not fixed |
|---|---|---|
| High | Disk drives running out of spaceall servers | When a drive fills, databases stop accepting changes and applications fail. |
| High | Slow disk response1 server | Slow storage makes every application that uses these databases slower. |
| Medium | Very large, mostly empty transaction logs3 occurrences, all servers | They hold disk space that other databases may need. |
| Medium | Out-of-date query statisticsall servers | Queries can pick slow plans. |
| Medium | The temporary database (tempdb) is not set up the recommended way1 server | It can slow every busy application. |
| Medium | Query Store has stopped recording1 server | No history is kept to explain slow queries. |
| Medium | Transaction logs with far too many internal segments1 server | Startup, restore and log backup are slower than they should be. |
Plus 31 low-priority notes in this area.