Skip to content

Instantly share code, notes, and snippets.

@nanoDBA

nanoDBA/Proposed SQL Server Patching Approach.txt

Last active February 26, 2023 19:37
Show Gist options
  • Save nanoDBA/c1712c96e5c7163d23858fa2b8d55540 to your computer and use it in GitHub Desktop.
Save nanoDBA/c1712c96e5c7163d23858fa2b8d55540 to your computer and use it in GitHub Desktop.
Download ZIP
An approach I've been using for the last 4 years or so to deploy SQL Server Cumulative Updates
Raw
Proposed SQL Server Patching Approach.txt
Proposed SQL Server Patching Approach
We do not patch to the absolute latest cumulative update(CU).
Rather, we strive to patch to the cumulative update(CU) that
was released without any intermediate releases(such as hotfixes)
between it and the most recent CU. Basically N-1 as long as
there aren't any hotfixes. If there were hotfixes then we'll wait
until two CU subsequent releases have occurred
without hotfixes in between the two to deploy the CU.
This minimizes the need to uninstall patches if they are
withdrawn by Microsoft. This also minimizes the need
to "patch the patch" when there are hotfixes / security
updates / withdrawals for a given CU.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment