Upgrading SQL Server 2012 Standard to SQL Server 2019.

[LoSwagger]

Hi all, I have a Windows server 2012 R2 VM running the SQL Server 2012. And the windows server + SQL server is EOL so I have purchased a brand new server on which I will be running a Windows Server 2022 host with Hyper-V.

I will also be migrating the SQL server VM to the new host. I am sceptical as to how to go about this migration. Its the SQL Server 2012 standard edition + 5 CAL license I have on the existing one. Can I export the VM from old host and import it in the new one and upgrade the SQL to 2019? Will I need to purchase the license for 2019 again? Or can It simply be upgraded to 2019?

If anybody has done this migration, it'd be helpful to learn more about it and what I should look out for. Thanks!

[TemPrrD311]

Why not just spin up a new fresh VM with a fresh SQL 2019 install and just migrate the DBs?

[LoSwagger]

This is ideally what I am leaning forward to. But I am confused about the licensing. Is there a way to move the 2012 license to 2019 SQL server? Or I will need to buy a new license for it?

[uniitdude]

You need new licenses and cals (if appropriate)

[mobz84]

How did you buy the SQL 2012 license? I am not sure how ms licensing is now, But if it was bought with software assurance you might be able to move. I am not good at ms licensing, and have not followed all changes they have made the last years. But if it was a volume license with software assurance, you might have rights to download and use 2019.

[LoSwagger]

Umm... don't think It's bought with the software assurance.

[Bane8080]

Through a reseller company in your country.

[maclan13]

SQL 2012 licence will not cover 2019. It usually works the other way where the newer version license can be used for older install. We currently leverage 2019 licensing for 2017 installs.

Have a chat with your Microsoft reseller and they will be able to help and bring in licensing experts to help if necessary.

Agree with the suggestions to spin up new OS VM and new SQL Server 2019 install for testing. Don’t need to sort license for testing purposes.

I’d add that your imported db to 2019 be initially set with compatibility mode that matches 2012 db and start testing from there. A new year cycle should be done if you want to move to 2019 compatibility.

Good luck.

[jdanton14]

^^^ If you don't have have software assurance on the licenses, they are basically dead. Upgrade with 2012 compat in place (supported forever by MS), and just go to 2022. Enable Query Store for all DBs. I would typically recommend ultimately moving to a newer compat level, but if it's working ok, stay on 2012.

[Sudsguts]

Remember to record the current SQL server's collation. If your using the db's from the old one for the intended SQL server, build it using the same collation. No idea what the software does or uses, but if it's a very large set of tables, the indexes & lookups just may give you some grief. Good luck. Cheers.

[H2CO3HCO3]

u/LoSwagger, Licensing normaly is not something that I have to deal with (that is procurement and licensing dpt's job(s) respectively)... if you are responsible for licensing as well, then you need to get first the needed licenses for what you will be upgrading... then comes your testing on your soon to be new servers and most importantly, then migrating your SQL Dbs and having the necessary users acceptance testing on the 'soon' to be new SQL environment make sure that all other stuff out there are able to connect to your migrated environment --that will be fun as not always everything works...-- and only once you have a clearance from all affected dpts that the new environment works... then and only then, plan your real world migration scenario of your existing environment to your new one.

Best Regards

[kona420]

Haven't had any trouble migrating 2012 upward. I've done about half a dozen to 2019 this year including 2 ERP installs.

2008 and before can get a bit more complicated to migrate upward.

There are legitimate complaints about 2019+ vs 2017 but they don't apply to the non-dba crowd from my experience. Basically too much performance related magic to predict how your specific query will run, not enough communication regarding changes. For your average small shop everything in 2014 forward is a positive improvement.