SQL Server would not start after patching: Script Upgrade failed because ##MS_PolicyEventProcessingLogin## had been granted permissions. Here is the fix.
SQL SERVER – FIX : Msg 35295, Level 16 – Log Backup For Database ‘DBName’ on a Secondary Replica Failed
During load testing, a log backup on a secondary replica failed with Msg 35295 because the last backup LSN was ahead of the redo LSN. Here is why.
SQL SERVER – Queries are in KILLED/ROLLBACK State with Wait PREEMPTIVE_OLEDB_RELEASE
After a network outage, queries stayed in KILLED/ROLLBACK with the undocumented wait PREEMPTIVE_OLEDB_RELEASE. What I saw and how to clear them.
SQL SERVER – Installation Error – The Specified Driver is Invalid
SQL Server setup failed for several features, and the setup logs said ‘The specified driver is invalid’. Here are the symptoms, the cause and the fix.
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.
Why to Use SQL Server Configuration Manager Over Services applet (services.msc)? – Interview Question of the Week #112
Why use SQL Server Configuration Manager Over Services applet (services.msc) to change a service account? The reasons, from permissions to passwords.
SQL SERVER – How to Apply Patch in AlwaysOn Availability Group Configuration?
A Patch in AlwaysOn Availability Group needs a sequence matched to the topology. I start this two-replica example with the secondary.