The Schema Changes History report can say it has no data to show. A client saw this message in SSMS. Check that default trace enabled is 1, make a schema change, and run the report again.
Visible Offline Schedulers: Find CPUs SQL Server Ignores
Visible offline schedulers are CPUs that Windows shows and SQL Server refuses to use. This post reads the scheduler status with tested queries, compares it with the CPU count and affinity, and explains the two common causes. It also shows the statement that returns the CPUs to automatic affinity.
Query Store On or Off for Every Database: Review First
To turn Query Store on or off for every database, you need one statement per database, because there is no server switch. This post builds a tested script that writes the statements, lets you read them and then runs them in one batch. It also covers READ_ONLY mode and the model database.
Query Store Status for Every Database in SQL Server
Query Store status for every database takes two queries, and the first is not enough. This post builds four demo databases, shows why the is_query_store_on flag hides frozen and read-only states, and runs one script that reads the real state of each database. It also shows what Query Store costs in memory.
SSMS Command Timeout: What the Execution Time-out Does
The SSMS command timeout is the number of seconds a query window waits before it cancels a batch. This post lists the four places a time-out can come from and reproduces a client time-out with sqlcmd and PowerShell. It also shows how an Extended Events session proves that the client gave up.
SSMS ROWCOUNT Setting: Why Your Query Stops at 100 Rows
The SSMS ROWCOUNT setting limits every query in a window to a fixed number of rows, and it can change the plan as well. This post shows the effect on rows, reads and plan with a tested demo, how to check your own session and why UPDATE statements stop at the limit too.
Configuration Manager WMI Error: Cannot Connect to WMI Provider
A Configuration Manager WMI error blocks SQL Server Configuration Manager with the message that it cannot connect to the WMI provider. This is a second way to fix it, using mofcomp with the file for your SQL Server version. If mofcomp does not succeed, my earlier post has more steps.