Compatibility level lag after SQL Server upgrades
Upgrading the engine without raising compatibility level leaves performance features and cardinality estimator behaviour on the table.
Moving to a newer SQL Server version is only half an upgrade. Many databases still run at an old compatibility level, freezing optimiser behaviour in the past.
Why teams delay
- Fear of plan changes
- No baseline or Query Store to validate
- “If it works, don’t touch it” after a stressful migration
Fear is rational. Permanent avoidance is not a strategy.
What you gain by moving carefully
- Modern cardinality estimator behaviour
- Access to newer T-SQL and optimiser improvements
- Alignment with vendor support expectations
Safe path we recommend
- Enable Query Store before the change
- Capture a workload baseline
- Raise compatibility in a controlled window
- Watch regressions; force good plans where needed
- Keep a rollback plan
Health-check role
We flag compatibility lag and upgrade leftovers (trace flags, deprecated configs) so the business can schedule a proper optimisation pass — not a surprise weekend firefight.
Need hands-on SQL Server help?
Allay Data Solutions offers maintenance, tuning, and assessments from Port Elizabeth, South Africa.