SQL Server 2008 to SQL Server 2022

Question

SQL Server 2008 to SQL Server 2022

Skybvi

SSCoach

Points: 15130
More actions
June 23, 2025 at 12:46 pm

#4611960

Hi,
Is it possible to upgrade from sql server 2008 to sql server 2022, considering we have hardware req fulfilled?
Or like we have to upgrade to sql server 2014/16 midway and then from there to sql server 2022
A normal backup and restore will suffice?
Any ideas ?

Regards
Sushant Kumar
July 17, 2025 at 7:42 am

This was removed by the editor as SPAM

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Mr. Brian Gale SSC-Insane Points: 24861 More actions · Answer 1

My advice - don't trust random people on a forum - trust the source. Check the Microsoft Docs:

https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022?view=sql-server-ver17

Upgrading to 2022 requires a min version of 2012 SP4.

Now, that being said, I don't like upgrading and skipping major versions. Too many things can go wrong and fixing it can be a huge pain in the butt. My approach to go from 2008 to 2022 would be to start with base 2008 R2 and test things. If things are good, then go to the latest 2008 R2 and retest. Then repeat with 2012, 2014, 2016, 2017, 2019, and finally 2022. LOTS of upgrades with that path, but lowest risk.

Plus it depends on if you are doing in-place upgrades OR migration (backup/restore on new instance) upgrade. In place is nice in that you get to keep all system database objects (logins for example). Migration upgrades are nice because it makes a rollback easy - turn the old instance back on. Migration upgrades also come with a bit of risk because you end up with a new instance name. So any applications that are explicitly looking for that instance will need to have connection string information updated. In place upgrades keep the same connection string, but rollbacks are a LOT more difficult and may even be impossible.

The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

Johan Bijnens SSC Guru Points: 135521 More actions · Answer 2

Don't perform "in-place" upgrades!

You'll want to migrate to an new ( and supported ) OS anyway.

Request 2 OS : 1 temporary - 1 permanent target

on the temporary, install SQL2014 with its latest CU ( CU14 )
- Restore your SQL2008 db(s)
- perform dbcc checkdb !
- create a new backup
- copy/move bak files to target server
On the target server:
- install your target version of sql server
- restore the needed databases
- perform dbcc checkdb !
- update all statisitcs
- use dbatools to copy user(s) , credentials, proxies, sqlagent jobs, ....

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

EdVassie SSC Guru Points: 60527 More actions · Answer 3

In your position, where the source environment is old and the target is new, I would aim to do it in the fewest steps. For you this means an intermediate host of SQL2014 SP4.

The intermediate is there as a necessary evil. I would not bother with any application testing at the intermediate level, but I would run some SQL scripts to confirm the restore has delivered a useable database.

It is at the target level that the application testing should be done. For me, who cares that the app had issues (say) on Win2012, Win2016 or SQL 2019, when the target is to get it working on Win2022 and SQL2022.

Focus the troubleshooting on the target environment. The business need is the target environment, so that is the only place it needs to work. You already know there are many differences between source and target, so don't expect everything to work first time.

Do what you should normally do - triage the problems into those that must be fixed before go-live and the technical debt that can be scheduled to be fixed later. Also avoid any nice-to-have upgrades as these can expand to fill months of work. The focus should be on getting the MVFS working on the target environment and fixing the rest later.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Abhinav Grasshopper Points: 24 More actions · Answer 4

Specefic to your question ; You can just do a direct backup and restore to new instance. Rest I am sure you know how to deal with migration.

https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022?view=sql-server-ver17&utm_source=chatgpt.com

"A backup taken on SQL Server 2008 (10.0.x) and later, can be restored to SQL Server 2022 (16.x) without changing its compatibility level, as long as the database backup has a compatibility level of 100 or higher."

Thanks,
Abhinav

VastSQL SSC-Dedicated Points: 36246 More actions · Answer 5

Skybvi wrote:

Hi,
Is it possible to upgrade from sql server 2008 to sql server 2022, considering we have hardware req fulfilled?
Or like we have to upgrade to sql server 2014/16 midway and then from there to sql server 2022
A normal backup and restore will suffice?
Any ideas ?

If you going for a side by side upgrade you can do log-shipping from 2008 to 2022 and AFAIK thats the easiest and simplest way to upgrade. Just make sure you move the jobs, logins, audits, extended events and other objects.

The downtime will be minimum and you can individually makes the databases online.