-
SQL Server Won’t Start After Patching: msdb 110_upgrade.sql Failed With Error 574
Skip to the bottom of the post for the TL;DR section for the on-call DBA where you can see an immediate cause and solution. SQL Server won’t start and at first, I couldn’t figure out why. When I logged off for the day on Friday, everything was happy, but when I logged on Monday morning,…
-
Did A CU Ever Get Applied? I Found The Answer In The SQL Server Update Cache
I was investigating the other day if a specific Cumulative Update (CU) had ever been applied to a SQL Server. The usual way I would go about this is to look at the Update History in the Control Panel by going to the search bar -> Search for Control Panel -> Programs -> Under Programs…
-
How I Use Python To Automatically Download And Stage SQL Server CUs And GDRs
Patching is such an important part of ensuring your MS SQL Servers are secure, reliable, and resilient. As important as it is, it’s still a tedious process. You have to chronically check for patches (hopefully you don’t have your servers running SQL to auto download and apply patches via Windows Update), look at breaking changes…
-
Database Crash Recovery Takes Forever After Planned Manual Failover
Weekend Patching, Business As Usual Today I was patching a bunch of servers at a client as Microsoft released their most recent Security Patch for SQL Server that addresses an exploit / vulnerability found after patch Tuesday. Read more on it here. I went through the normal patching routine for an AG; working through all…
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
DBA Unfiltered 