Problem page
SQL Server failed upgrade
Use this when a version change already went wrong, the rollout confidence is damaged, or the next attempt needs much tighter control.
MKsql server / planned-change
Upgrades, migrations, patching risk, and the production change work that needs rehearsal instead of optimism.
Start here when the estate is moving and the main risk is weak rehearsal, soft rollback thinking, or change work that has already outgrown improvisation.
Problem page
Use this when a version change already went wrong, the rollout confidence is damaged, or the next attempt needs much tighter control.
Problem page
Use this when the estate is moving and the real question is whether the plan, rollback, and dependency picture are strong enough yet.
Problem page
Use this when the version is aging, the support picture is messy, or patching has started to feel like change work nobody really owns.
Live guides
Some of these pages still live under /hub. What matters here is that they read as one working lane instead of a flat list of disconnected SQL topics.
CU vs GDR, build-number interpretation, and how to separate a patch decision from a real upgrade decision.
Live SQL Server supported-build and version-history reference built from Microsoft's update source.
Version-lifecycle planning, rollout risk, rollback thinking, and the production checks around major SQL changes.
Inventory, dependency mapping, rehearsals, rollback design, and cutover planning for real production moves.
Service paths
Project and planned change
Upgrade and rollout support for version changes that need readiness review, rollback thinking, and calmer execution.
Audit and health review
Practical review for inherited estates, weak operational ownership, and environments that need a real fix order.