A client’s SQL Resource would not come online on either cluster node. The ERRORLOG showed a very slow recovery of a huge master database. Here is the fix.
SQL SERVER – SQL Server Cluster Resource Doesn’t Come Online Randomly
A client’s SQL Server Cluster Resource sometimes failed to come online after a failover to another node. Here is what caused it and how we fixed it.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘sqlagent100_msdb_upgrade.sql’ – Error: 5041: MODIFY FILE Failed
One more cause of the script level upgrade failure for ‘sqlagent100_msdb_upgrade.sql’: Error 5041, MODIFY FILE failed. Here is how I fixed it.
SQL SERVER – FIX: Msg 3009 – Could Not Insert a Backup or Restore History Detail Record in the MSDB Database
A backup finished but raised Msg 3009: could not insert a backup or restore history detail record in msdb. Here is why, with steps to reproduce it.
Restoring a Database That Has a Memory-Optimized Filegroup
The container behind a memory-optimized filegroup is a folder, and a restore must place it. Here is the error you get when you forget, and the fix.
Move the Master Database to a New Location in SQL Server
To move the master database, change its startup parameters in SQL Server Configuration Manager, stop SQL Server, move the files and start it again. This post explains why ALTER DATABASE can’t move master, reads the current paths with T-SQL, and lists the steps and the permission check that stops most failed moves. It also says what to do when the instance won’t start afterwards.
Finding User Objects in master Created by Accident
Find user objects in master, inspect their purpose and dependencies, and prepare a safe move without removing deliberate server helpers.