r/SQLServer • u/AngryPets • 4d ago
Solved Changes to SQL Server SECURITY Patching
SQL Server customers used to, effectively, have TWO options for deploying SECURITY fixes to their installed SQL Server instances:
GDR - security ONLY patches/updates (i.e., via Windows Updates/etc.)
only fixes directly related to SQL Server's attack surface.
CU - Security + ALL other bug-fixes (non-security), perf-enhancements/tweaks/options, and even (occasionally) new 'features', etc.
Take-away being that there were OPTIONS for DBAs/Admins relative to WHEN they could/would deploy ENGINE-LEVEL/BEHAVIOR-LEVEL changes - without having to sacrifice worries about security.
e.g., don't want a new, known, bug released on CUxxx but also don't want to leave your instances unpatched? GDR it is until the bug/issue in question has been fixed.
Fast forward to the past few months:
Microsoft is now bundling GDR fixes BOLTED-ON to (the most recent) CU.
i.e., IF you want security fixes to patch some fun vulnerabilities being discovered ...
then you're FULL on getting engine-changes as well.
While I'm not a HUGE fan of this, I ... get it - ish.
My question, though, is:
Has anyone seen this CHANGE 'documented' or mentioned in any public channels (or, cough, back channels; I mean, you could tell me, then I'd let you kill me, but I'd happily die with the answer tucked away into my brain) that would explain:
why (formally)
if this is ever going to go "back the way it was" (choice/options) and/or if this is the NEW path forward (sit down, shut up, and LIKE it).
TIA.
11
u/Harhaze 1 4d ago
You still have an option of using either GDR or GDR + CU. If you check for yesterdays release there are two GDR.
Or am I missing something?
EDIT: even tho GDR is "lower" it still fixes same CVEs.
| GDR name | SQL Server build version | SQL Server (sqlservr.exe) file version | Analysis Services build version | Analysis Services (msmdsrv.exe) file version | Knowledge Base number | Release date |
|---|---|---|---|---|---|---|
| CU10 + GDR | 17.0.5045.3 | 2025.170.5045.3 | 17.0.25.223 | 2025.170.25.223 | KB5129299 | November 10, 2026 |
| GDR | 17.0.1155.3 | 2025.170.1155.3 | 17.0.25.223 | 2025.170.25.223 | KB5132748 | November 10, 2026 |
3
u/AngryPets 4d ago
Ah. Perfect - thanks!
I am (was) conflating the default behavior you 'get' from/via Windows Updates (where the GDR+CU option is pushed) with there somehow "no longer being" GDR ONLY fixes.
Really appreciate the quick reply. Solution verified.
1
u/reputatorbot 4d ago
You have awarded 1 point to Harhaze.
I am a bot - please contact the mods with any questions
1
15
u/BrentOzar 4d ago
What you’re saying is simply incorrect.
Go to SQLServerUpdates.com to get either the plain RTM GDRs, or the CU GDRs. Still there. Always have been.
2
u/AngryPets 4d ago
Thanks Brent.
Appreciate the quick reply. I've been using https://sqlserverbuilds.blogspot.com/ and then clicking on the KB links ... which link directly to the CU+GDR links vs ... options for either.
That, and I was conflating what's pushed by windows updates in smaller orgs with more robust options via WSUS/etc. where (i assume) admins can pick/chose.
Thanks again!
1
u/Ancient-Bat1755 2d ago
Does cu include windows performance fixes or will that be an os update?
1
u/AngryPets 2d ago
Those would come from an OS update.
CU only includes (potentially) SQL Server perf fixes.1
•
u/AutoModerator 4d ago
After your question has been solved /u/AngryPets, please reply to the helpful user's comment with the phrase "Solution verified".
This will not only award a point to the contributor for their assistance but also update the post's flair to "Solved".
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.