What SQL ConstantCare® Looks For

SQL ConstantCare® analyzes your data looking for health and performance issues that cause user pain. Here are the things we check for and the number of servers where we found this problem this month:

Backup

• Back Up Your TDE Certificate – 137 servers affected
• CRITICAL: Take a Full Backup – 370 servers affected
• CRITICAL: Take a Log Backup – 353 servers affected

Corruption

• CRITICAL: Database Corruption Detected – 5 servers affected

Patching

• CRITICAL: Dangerous Build with Known Corruption – 11 servers affected
• CRITICAL: Dangerous Build with Security Bug – 26 servers affected
• Update Available – 1,696 servers affected
• Upgrade to 2016 SP1 for Freebies – 15 servers affected

Performance

• Auto-Update Stats Disabled – 40 servers affected
• Change Repetitive Maintenance Plans – 105 servers affected
• Consider Enabling Query Store – 1,029 servers affected
• Consider Migrating to a 64-Bit Server – 22 servers affected
• Consider Re-Enabling Indexes – 129 servers affected
• CPU Schedulers Offline – 52 servers affected
• CRITICAL: Poison Wait: CMEMTHREAD – 35 servers affected
• CRITICAL: Poison Wait Detected – 469 servers affected
• CRITICAL: Poison Wait: Serializable Locking – 131 servers affected
• Deadlocks Occuring – 2 servers affected
• Default Parallelism Settings – 110 servers affected
• Disable Auto-Close – 70 servers affected
• Disable Auto-Shrink – 101 servers affected
• Drop Unused Indexes – 150 servers affected
• Duplicate Indexes – 40 servers affected
• Enable Instant File Initialization – 392 servers affected
• FYI: Resource Governor Enabled – 103 servers affected
• FYI: Server Triggers Enabled – 244 servers affected
• FYI: Unusual SQL Server Edition – 117 servers affected
• Heap Needs to Be Rebuilt – 585 servers affected
• High Memory Use for In-Memory OLTP (Hekaton) – 3 servers affected
• Low Waits: SQL Server Was Bored This Week. – 2,367 servers affected
• Memory Dangerously Low – 22 servers affected
• Memory Dangerously Low in NUMA Nodes – 23 servers affected
• Memory Leak – 7 servers affected
• Memory Nodes Offline – 10 servers affected
• Memory Pressure Affecting Queries – 62 servers affected
• Plan Cache Erased Recently – 217 servers affected
• Remove the Shrink Database Job – 116 servers affected
• Remove the Shrink Database Plan – 22 servers affected
• Server Power Changed – 100 servers affected
• Set Fill Factor Higher – 385 servers affected
• Set MAXDOP to Reduce Parallelism Waits – 106 servers affected
• Set Max Memory Lower – 198 servers affected
• Too Much Free Memory – 375 servers affected

Planning

• Database Size Increased – 205 servers affected

Query Tuning

• Compilation Timeout – 704 servers affected
• Joining to Table Valued Functions – 586 servers affected
• Queries may have non-SARGable predicates – 1,057 servers affected
• Query Forced to Run Single-Threaded – 803 servers affected
• Query Slowed by Implicit Conversion – 387 servers affected
• Query with Missing Index Request – 709 servers affected

Reliability

• Call Microsoft to Report Memory Dumps – 131 servers affected
• Check for Broken Log Shipping – 70 servers affected
• Check for Corruption ASAP – 820 servers affected
• Check Unusual Database States – 202 servers affected
• Disable Priority Boost – 28 servers affected
• Enable Checksums for Corruption Detection – 320 servers affected
• Enable Remote Admin Connections – 567 servers affected
• Full Text Indexes Not Updating – 49 servers affected
• In-Memory OLTP Transaction Errors – 4 servers affected
• Move TempDB Off the C Drive – 174 servers affected
• Move User Databases Off the C Drive – 209 servers affected
• No Cluster Nodes Available for Failover – 9 servers affected
• Restart to Correct TempDB File Error – 10 servers affected
• Server Keeps Restarting – 157 servers affected
• Transaction Log Larger than Data File – 735 servers affected
• Unsupported Build of SQL Server – 458 servers affected

Let’s get started: what will we find on your SQL Servers?