When did you last time patch your SQL Server? I often discuss this question with my clients, I get many different kinds of answers.
SQL SERVER – Check for Update in SSMS
How to check for an update in SSMS depends on the installed generation. My fintech-customer walkthrough showed SSMS 18 settings.
SQL SERVER – Upgrade Error: Microsoft NET Framework 4.0 Installation Has Failed With Exit Code – 2146498511
The solution of error Microsoft .NET Framework 4.0 installation has failed with exit code -2146498511 which was faced during SQL Server upgrade
SQL SERVER – Fix Error – Login failed for user. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401)
I recently had a very simple and interesting error received while I was performing an upgrade mode with Docker and Persistence Storage for my upcoming workshop.
High CPU Consumption in SQL Server: Where to Look First
High CPU consumption in SQL Server comes from a handful of causes, and a short checklist finds them in order. This post reads the scheduler queue, ranks cached queries by CPU, and checks the Common Criteria Compliance setting that caused a known CPU problem after upgrades. It ends with the update that fixed that case and the questions to ask before you add cores.
Checking That a Patch Really Installed
Checking That a Patch Really Installed means comparing full versions, reading Setup summary logs, and confirming the startup error log.
GDR or CU: Choosing Your Update Branch
Choose GDR or CU for SQL Server by understanding security and cumulative branches, checking the exact build, and testing a branch change.