410
Our plan is to upgrade from Dynamics GP 2013 to GP 2016. GP 2016 requires at least SQL Server 2012, but we're currently running SQL Server 2008, so our first step is to upgrade to SQL 2014. We intend to do an in-place upgrade of SQL.
Suggestions regarding GP in this scenario? Simply put, if we upgrade JUST the SQL for a week or two, what actions, if any, will we need to take on our GP 2013?
Thank you...
*This post is locked for comments
Thank you both for those helpful answers... Will move forward.
Step 9 > Use KB 878449 to migrate databases and GP user logins over to the new SQL instance. If you're doing an in-place upgrade of SQL, you don't have to worry about this step.
Integration Manager is a separate process than upgrading the GP databases GP 2016, but yes, there is a GP 2016 version of IM that you'll need to install.......you don't need to 'upgrade' the IM database or source files.
GP 2013 is compatible with SQL 2014, as long as you're on GP 2013 R2, which is 12.00.1745 or higher. If you're on R2 or higher, upgrading SQL to SQL 2014, while still on GP 2013 shouldn't cause an impact.
As Jeff mentioned, a test upgrade is always the best option!!
Thanks
Thank you for your complete and thoughtful reply. First, our main (only?) reason for not going to GP 2018 is that it doesn't seem to be as well-represented on this and other forums. Is it soup yet? I can look this up, of course, but is GP 2018 good with SQL 2014? (SQL 2014 is as far as we can go without a lot of extra licensing.)
We are on GP 2013 R2 (12..00.1745), and we understand that there may be a minor update to that version. We'll do that first.
Will you provide a little clarification on Step #9? What steps are required to do that?
Finally, we're running Integration Manager and Table Import. Any apparent conflicts there?
Again, thank you for a complete answer... rare these days.
Hi BrainMan
The approach you take is going to depend on which version of Dynamics GP 2013 you are currently on.
GP 2013 is supported on SQL 2008 and SQL 2012. However if you are on GP 2013 R2 it is also supported on SQL 2014.
GP 2016 is supported on SQL 2012, 2014 and 2016.
I always recommend a test upgrade to ensure everything goes smoothly so that any issues can be ironed out before the production upgrade to minimize down time.
Based on what you told me and wanting to do an in place upgrade, here is what I would do.
1. Backup my databases
2. Install the latest service pack for GP 2013 that will allow you to upgrade to GP 2016 R2.
3. Upgrade your Dynamics and company databases to GP 2013 latest service pack
4. Upgrade your reports and forms.dic files
5. Backup databases
6. Upgrade any 3rd party products you may have to a version that will allow you to upgrade them to 2016 R2
7. Backup databases
8. Upgrade SQL 2008 to SQL 2014
9. Upgrade your Dynamics and company databases to SQL 2014
10. Backup databases
11. Install Dynamics GP 2016 R2 with latest service packs
12. Upgrade databases to GP 2016 R2
13. Upgrade reports and forms dictionaries to GP 2016 R2
14. Backup databases
15. Upgrade any 3rd party products you use
16. Backup databases
Be sure to read the notes on upgrading to GP 2016 R2 and ensure that you have the correct versions installed for the upgrade path.
Any reason why you are not going to GP 2018?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (