Share
ReportHi,
Can anyone tell me whether Microsoft Dynamics GP 2013 R2 compatible with SQL Server 2016.
Any guidance will be highly appreciated.
Regards
Tom
*This post is locked for comments
You’re offline. This is a read only version of the page.
1,750
Hi,
Can anyone tell me whether Microsoft Dynamics GP 2013 R2 compatible with SQL Server 2016.
Any guidance will be highly appreciated.
Regards
Tom
*This post is locked for comments
Yes Mark, you can do that. Just follow the procedures outlined in KB article 878449 as I previously indicated.
So this thread has been confusing.... bottom line question is
Can I upgrade the old server (GP2013R2 build 1745 on SQL2008R2) to the new server (GP2016R2 on SQL2016) using the database transfer method?
Hello,
Is there any formal documentation on doing both upgrades at the same time? We are also on GP 2013 R2 / SQL Server 2008 R2 SP2 / Windows Server 2008. My plan was to upgrade to SQL 2012, then Windows Server 2012, promote to GP 2016, and finally promote to Windows Server 2016 and SQL 2016. We also use SmartConnect and Mekorma check printing. Any direction is greatly appreciated. Thanks, -dn
The goal for myself, and likely others as well, was not to "Run" GP 2013R2 on SQL 2016. It was to Patch 12.0.1745 to a level that GP 2016's upgrade would support, not to run GP itself, not do any accounting work, or add new companies.
I have got a whole set of shiny new servers (ok, VM's) ready for my first upgrade test. I plan to restore the GP 2013R2 data here (on the new SQL server) and install a copy of GP 2013 R2. Test here. Then patch to the needed level ("12.00.1826 or later"), in this case I believe 12.00.2104. Test here. Then run the GP 2016 upgrade. Following all needed table checks and scripts along the way, of course.
I would have liked to start off the new GP 2016 servers fully modernized to the latest of everything in one pass, saving a future SQL upgrade, but since SQL 2016 may cause issues for that intermediate 12.00.2104 patch, I don't want to risk it.
This IS NOT an endorsement of GP 2013 R2 on SQL Server 2016, but if this is to work in some way, the only way I can think of it is to follow the procedures outlined in KB article 878449 (support.microsoft.com/.../878449) to get the databases over to SQL Server 2016. The downside to this is YOU WILL NEVER BE ABLE to run GP 2013 R2 Utilities to add new companies.
By the same token, this KB article should be followed to move your databases to SQL Server 2016 and, then and only then, run the GP 2016 upgrade.
Thanks Victoria!
Being the guy I am, that just makes it a challenge, and I wish I had the time and resources to give it a go. Unfortunately, my upgrade is going to be complicated enough with all of the twisted customizations I inherited. Ah well!
I appreciate the work you do and all the help you provide to the GP community.
David Morinello – Senior Dynamics GP Systems Architect
Ascend Learning
11161 Overbrook Road | Leawood, Kansas 66211
d 913-661-6425| www.ascendlearning.com
David,
I am not aware of any way to fool the system the way you are asking. I have seen plenty of posts from people who have tried and not been successful. What we typically do in these situations is set up a test virtual server that is only used for the duration of the test (and sometimes as an interim step for the live upgrade) that has a lower version of SQL on it. Then you can go to GP 2016 with SQL 2016 on a new server without having any old versions of anything on there cluttering things up.
I will be running a first test upgrade of GP 2013R2 to GP 2016 soon.
Since I have to patch 2013R2 (12.0.1745) first to bring it to a supported patch level for the GP 2016 upgrade piece, I assume I cannot have SQL 2016, set at a lower compatibility level, with the restored GP 2013 R2 data? It sure would be nice if there was an easy way to slip the SQL 2016 into the upgrade. Is there no way to fool the GP patch just for the time necessary for the upgrade to complete?
Has anyone tried to make this work?
Thoughts?
Victoria,
Well I started doing the same, like running the patches in the same environment and then take the DB to SQL 2016 and then to GP 2016.
Anyways thanks a lot for all your valuable advise and support.
Cheers
Tom
Tom,
Gotcha, so you are seeing the proof of what I was saying. You may run into some issues if you're actually running GP 2013 R2 on SQL 2016. I would not recommend upgrading to SQL 2016 until you upgrade to GP 2016. You should be able to upgrade both at the same time with no issues. I have done this for many customers.
If you are currently setting up a test upgrade and you are replicating the current environment and testing the upgrade, you are better off installing both SQL 2008 R2 and SQL 2016; use SQL 2008 R2 for the GP 2013 R2 app, then move to SQL 2016 for the GP 2016 app.
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,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (