Notifications
Announcements
No record found.
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
Hi Tom,
No, GP 2013 R2 is not supported on SQL 2016. It might look like it works if you try it, but you will eventually run into problems if you try to add a new company or when you go to upgrade to a newer version of GP.
Here is a link to the system requirements for GP 2013: mbs.microsoft.com/.../mdgp2013_system_requirements
Thank you very much mam for your prompt reply.
Actually I was trying to do the migration from GP 2013 R2 to GP 2016 with SQL Server 2016 in place.
While trying to run the GP2013 R2 utilitites with SQL Server 2016 encountering the error
"Your current SQL Server is not a supported version".
Any patches are there to overcome this or should I wait.Please advise.
If you are upgrading to GP 2016, why are you running GP 2013 R2 Utilities?
Hi Victoria,
First I was trying to replicate the current environment i.e GP 2013 R2 with SQL Server 2016. B'coz currently we are using GP2013 R2 with SQL Server 2008 R2 and the important thing is the DB up gradation and GP migration will not happen parallely.
So first I need to check whether GP2013 R2 works with SQL Server 2016 to start with :(.
Hope you got my concern.
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.
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
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?
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.
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
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.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
mtabor 1
