Msg 17113 stops SQL Server at startup with an error opening master.mdf. I caused it myself by changing a startup parameter, and the file was still in place. The ERRORLOG showed the clue: the parameter name was wrong, and the fix was in Configuration Manager.
SQL SERVER – Script level upgrade for database master failed – Error: 4860, Severity: 16, State: 1 – Cannot bulk load. SqlTraceCollect.dtsx does not exist
SQL Server would not start after patching: script level upgrade for database master failed with error 4860, SqlTraceCollect.dtsx does not exist. The fix.
Error 9003: Log Scan Number in master Is Not Valid
Error 9003 on the master database means SQL Server cannot recover master and will not start. The master files were corrupt. We rebuilt the system databases, started the instance in single user mode and restored master from a backup.
Database Scoped Configurations Changed From Their Defaults
One column in sys.database_scoped_configurations finds every setting that differs from its default. I show how to use it, and where it goes blind.
How to Remove Database Mail History and Stop msdb Growing
Database Mail history stays in msdb until you delete it, so the sysmail tables can grow for years. This post measures the tables, then removes the history with the two supported procedures instead of direct deletes. It also covers a month by month loop for a big backlog and a schedule.
Master Database in SQL Server: What It Holds and How to Protect It
The master database is the one database a SQL Server instance cannot start without. It stores logins, linked servers, server settings and the list of databases. The tests here show what master holds, what it does not, how to back it up with CHECKSUM, how to check the backup, and what a master restore involves.
SQL SERVER – Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’
After a patch, my SQL Server would not start because upgrade step ‘sqlagent100_msdb_upgrade.sql’ failed with error 537. Here is how I fixed it.