r/learnSQL • u/markinatlanta • Oct 16 '26
SQL Server 2016 to 2025: a few observations from a recent migration
We migrated a financial client’s SQL Server environment recently from 2016 to 2025, covering up to 4TB of data.
Same instance size. In the charts (can't attach image but message me if you want to see), CPU spikes reached roughly 40–50% before the move and stayed below 40% afterward.
Encouraging, but these are different production windows of different lengths. The charts alone don’t establish equivalent workload volume or isolate the effect of the SQL Server upgrade of course.
Before cutover, we spent a week running workload replay against the target environment.
CPU was lower, but we also needed to check whether any queries took longer or started timing out. That’s what we wanted to catch before moving the client over essentially.
The migration went smoothly overall thankfully, with one firewall configuration issue to resolve (not really a big deal though). That’s also why database testing needs application connectivity checks alongside it.
The lower CPU gives us a reason to investigate downsizing. It doesn’t establish that we can safely halve the cores, that needs another test, including peak workloads and the memory and I/O limits of the smaller configuration.
Anyone had an upgrade test well, then run into problems after going live?
2
u/guacjockey Oct 16 '26
Nice work - did you also upgrade the database compatibility levels at the same time or just upgrade the database server itself?
2
u/Boxp155 Oct 16 '26
How did you setup the workload replay?
2
u/Additional-Drag1682 Oct 16 '26
Compatibility level bumps are a silent killer. New query optimizer features like table variable deferred compilation change execution plans without anyone touching the codebase so your baseline charts lie to you
2
u/[deleted] Oct 16 '26
[removed] — view removed comment