We are upgrading to a PILOT Environment for 2024 from 10.2.500.40. and have questions about upgrading the SQL Server 2016 to SQL Server 2017 in order to have both Environments work as the same time. There is very limited information regarding this in the Epicor Installation Manual or Knowledge Base.
These are two separate servers, correct? What questions do you have. You can move a database from an older version of SQL to a newer, but you aren’t going to be able to go backwards. Since we’re talking about a pilot environment, I assume that’s not a problem.
There are on the same server but Kinetic does not work on SQL Server 2016. We need to upgrade to 2017 for the report server to work. We are looking for some kind of instructions on how to do this with breaking the report server.
Ideally, you would want to run that on a different server. That would be safest.
It would probably work, but do you really want to run your production environment in an unsupported configuration? If I had no other options, I would try getting Kinetic to work on SQL 2016 first. I don’t know if that is simply unsupported or doesn’t work, but I’d rather have my piloting environment be unsupported rather than my production one.
Documentation for installation of Kinetic says it has to be SQL 2017 or greater.
Configuring Reporting Services
Before you configure the reporting services, either install SQL Server Reporting Services
(SSRS) 2017 with SQL Server 2017, SSRS 2019 with SQL Server 2019, or SSRS 2022 with
SQL Server 2022. Be sure to install using Native Mode so you can print standard reports.
1 Like
Correct but what @Chad_Smith is saying you’d ideally install Kinetic on a separate server from your 10.2 server. SQL 2016 is long in the tooth and easy to speculate your server hardware is too.
I understand what you are saying.
If this is just an investigation as to " let’s see how it goes first". I would be doing this on a Virtual machine and leavre your Pilot environment alone totally.
Review the upgrade guides on Epicweb.
Standing up a new environment to do this is not without its challenges, however it will help you with a better understanding of how it all hangs together. There are some differences between 10 and Kinetic
As always happy to help further
3 Likes
Chad,
Just to clarify, you are saying to install Kinetic on a separate SQL Server?
Yes, the ideal situation would be to have two completely separate environments. One for your production environment and another for your testing environment.
Check with your IT support folks on licensing rules but I think you can spin up a new , more current version of the server and SQL in Eval mode for 180 days do do your testing. Just remember you can move data from older SQL to newer, but you can’t move from newer SQL back to older versions. So the data is a one way trip.
1 Like