A greyed-out Agent node and a stopped Agent service are two different faults, and the sp_configure fix only cures one. One query tells them apart, then the Agent’s own log gives the reason.
A database comes back from a restart marked SUSPECT and error 926 refuses every connection. The real sequence: confirm the state, read the error log, then choose between EMERGENCY repair and the restore.
Error 1418 says the server network address cannot be reached and never says why. The error log names the fault, and then there are five checks in the order that finds it.
One line sets a login default database, and SQL Server never checks that the login can actually use it. The failure arrives at the next connection, with the same message whether the database is gone or just inaccessible.
SQL Server at 100 percent CPU describes four different problems. The five checks that separate them, in the order that finds the fault fastest, each handing off to the script that does the work.
Exporting a query to CSV looks like a solved problem. Set a comma as the delimiter, save the file, done. Then somebody opens it in Excel, a column has shifted, and a customer called Smith, Jones and Co has quietly turned into two fields.
A network-related or instance-specific error, error 53, error 40, error 26: which one you have decides where to look. The connection checks in the order that finds the fault, each one linking to the full fix.
Renaming a Windows machine is a two minute job. Renaming a Windows machine that happens to be running SQL Server is not, because SQL Server records the server name in its own metadata at install time and does not notice when the operatin…
There are two ways to get a CSV into SQL Server, and picking the wrong one costs you either an afternoon or a silent data loss.
A log backup fails with Msg 4214 when a FULL recovery database has no log chain yet. One check finds it and one full backup fixes it.