Currently on version 2024.2.
Sql server is 2017 , Windows is 2016
We want to upgrade to 2025.2.
Epicor guides says:
Is this really required or just a nice to have?
What issues will I run into upgrading these servers?
It will be fine from a technical standpoint. It will run. But Server 2016 and SQL 2017 is EOL. Unless you paid for ES. Just as a heads up.
You’ll want to upgrade to a newer versions as even Microsoft has them on extended support now. Could you run 25.2 on what you have? Sure, but why take the risk as 2027 is coming soon?
Server 2016
- Mainstream support for Windows Server 2016 ended on January 11, 2022.
- The product is currently in its extended support phase, which will continue until January 12, 2027.
- During the extended support phase, only security updates are provided, with no feature updates or non-security fixes.
SQL 2017
Yes, SQL Server 2017 is still supported, but it is currently in its Extended Support phase. Here’s a breakdown of its lifecycle:
- Mainstream Support for SQL Server 2017 ended on October 11, 2022. During this phase, Microsoft provided feature updates, bug fixes, and security patches.
- Extended Support began on October 12, 2022, and will continue until October 12, 2027. In this phase, only critical security updates and bug fixes are provided, with no new features or enhancements
I actually think you will run into issues with this, there is syntax that Epicor uses that is not supported in the older SQL Server versions.
I have seen this before, in particular BAQs that use SQL functions.
Following up on this. Should i do an in place upgrade of windows and Sql server or do a new VM and fresh install of both and restore from a back up for the DB?
I never do in place upgrades. I always find it cleaner to install fresh and restore. Too many weird issues with in place upgrades.
thats what i was thinking too.