To see progress while a long script runs, use RAISERROR WITH NOWAIT instead of PRINT. This post builds a progress loop, formats values with placeholders, and shows the percent sign trap that garbles a message. It also explains how severity decides whether a message stays inside a TRY block, and where the 2,047 character limit cuts a message.
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.
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
The specified driver is invalid error led to performance-counter files in this SQL Server 2012 case. Fresh installation media resolved the failure.
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.
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.