Error 913 means SQL Server could not find database ID 3, which is the model database, so the service will not start. A client had no backup of it and attaching the files failed. Rebuilding the system databases brought the instance back.
What is the Difference between SUSPECT and RECOVERY PENDING? – Interview Question of the Week #114
What is the difference between SUSPECT and RECOVERY PENDING? A reader moved databases to a new drive and they went into recovery pending. Here is why.
SQL SERVER – Script Upgrade – Server Principal ‘MS_PolicyEventProcessingLogin’ Has Granted One or More Permission(s)
SQL Server would not start after patching: Script Upgrade failed because ##MS_PolicyEventProcessingLogin## had been granted permissions. Here is the fix.
Specified Driver Is Invalid in SQL Server Setup: Error 0x84BB0001
The specified driver is invalid error stopped a SQL Server 2012 installation with code 0x84BB0001. The real clue sat in Detail.txt, in the performance counter files, and a fresh copy of the media fixed it. This post shows how to read the logs, check the counter files and confirm the media.
SQL SERVER – SQL Browser not Starting. Error – The SQL Configuration for SQL is Inaccessible or Invalid
After server hardening, SQL Browser would not start and the event log said the SQL configuration for SQL is inaccessible or invalid. Here is the fix.
Msg 17113: Error Opening master.mdf at Startup
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 – Fix: Error 946, Severity: 14 – Cannot open database ‘DB’ version 782. Upgrade the database to the latest version
Upgrading an AlwaysOn replica from SQL 2014 to 2016, databases got stuck and the ERRORLOG showed error 946, cannot open database version 782. Why and the fix.