Why upgrade now
Extended support for SQL Server 2008 and 2008 R2 ended in July 2019, for SQL Server 2012 in July 2022, for SQL Server 2014 in July 2024 and for SQL Server 2016 in July 2026. Without support there are no more security updates, unless you buy Extended Security Updates where Microsoft still offers them, which only postpones the problem.
New versions of Windows Server, drivers, backup and monitoring tools also drop old SQL Server versions one by one. The longer you wait, the bigger the jump.
Supported upgrade paths
There are two ways to get a database onto a new version: upgrade the existing installation in place, or install the new version on a new server and move the databases across. For old versions the second route is usually the only one, and also the safer one.
- In-place upgrade: SQL Server 2022 can upgrade SQL Server 2012 SP4, 2014 SP3, 2016 SP3 or a later version in place; SQL Server 2025 can upgrade SQL Server 2014 SP3, 2016 SP3 or later. From SQL Server 2008 there is no direct in-place path.
- Backup and restore on a new server: a backup made on SQL Server 2008 or later can be restored on SQL Server 2022 and 2025. The database is upgraded during the restore. This works for every version in this guide and leaves the old server untouched as a fallback.
- Log shipping or an availability group to a new server: for large databases with little room for downtime. The new server is kept in sync and you switch over in minutes.
Compatibility levels: the safety net
Every database has a compatibility level that determines how SQL Server interprets its queries. SQL Server 2022 supports levels 100 (SQL Server 2008) to 160, SQL Server 2025 levels 100 to 170. After a restore the database keeps its old level, so most code behaves as before.
That is a useful first step, not the end point: many optimiser improvements only apply at the newest level. Upgrade with the old level, turn on Query Store to record the current plans, then raise the level and fix any query that becomes slower.
What tends to break
Most of the work is not in the upgrade itself, but in features that have been removed or changed since the old version. Typical points of attention:
- Syntax that has been removed, such as the old outer join operators
*=and=*or the old form ofRAISERRORwithout parentheses - Deprecated data types such as
text,ntextandimage: they still work, but are a reason to plan a clean-up - Stretch Database, deprecated in SQL Server 2022 and discontinued in all supported versions since July 2024
- Newer client drivers (ODBC Driver 18, OLE DB Driver 19) that encrypt connections by default and check the server certificate, so applications and linked servers can fail to connect until certificates are in order
- Logins, SQL Server Agent jobs, linked servers, Database Mail and credentials: they live outside the database and do not move with a backup
- Query plans that change when you raise the compatibility level
A practical order of work
Start with an inventory: which features the code uses, which objects are deprecated, how large the database is. Then restore a recent backup on a test server with the new version, run the application against it and compare the results. Only then plan the switch-over, with a way back: keep the old server until the new one has run in production for a while.
How the free scan helps
The MigrateMyDatabase scan runs a read-only script on your database that collects the structure: tables, columns, indexes and which features your code uses. You paste the result in the page and choose SQL Server 2022 or 2025 as the target. The analysis runs in your browser and lists the objects that need attention, with a score per target. Nothing is uploaded, and the script reads no table data and no code text.
Questions
Can I restore a SQL Server 2008 backup on SQL Server 2025?
Yes. SQL Server 2022 and 2025 can both restore backups made on SQL Server 2008 or later. The database is upgraded during the restore and keeps compatibility level 100 until you raise it.
Can I skip versions, for example from 2012 straight to 2025?
With backup and restore, yes: you can go from any version in this guide directly to 2022 or 2025. An in-place upgrade to SQL Server 2025 needs SQL Server 2014 SP3 or later, so an older installation needs an intermediate step or a new server.
Should I choose SQL Server 2022 or 2025?
Both are supported for years to come. SQL Server 2025 has the longer support period and the newest features; SQL Server 2022 has been in use longer. Check which version your application vendor, backup software and drivers support.
Find out what breaks before you upgrade: run the read-only script, paste the result and pick SQL Server 2022 or 2025 as the target. Free, and nothing leaves your browser.
Start the free scan