Finance | Project Operations, Human Resources, ...

GP 2016 (16.0.553.0) and a 2019 SQL Server

(0) Share

Report

Posted on by LeAnn619oh

My client is moving servers and they have a 2019 SQL Server and 2019 APP Servers (we have 2 of them). The APP servers will be load balanced, but I need to install the software. When I go to run the application, I'm getting "Your current SQL server is not a supported version" message.

Can I get some guidance on my next steps or how to resolve? Would prefer to not have to upgrade GP right now if at all possible. Thanks!

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (11)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

As GP 2016 is not compatible with SQL 2019 you have two options:

Option One: Upgrade GP to 18.3

Option Two: Downgrade SQL to SQL 2016

https://mbs.microsoft.com/customersource/northamerica/GP/learning/documentation/system-requirements/MDGP2016_System_Requirements

Was this reply helpful? Yes No
Suggested answer

Justin Sutton on at

Like (1)

Report

Hello LeAnne,

Richard is spot on!

Dynamics GP 2016 does not work with either Windows Server 2019 or SQL Server 2019.

You will need to upgrade to GP 18.2 at a minimum for both (the jump to 18.3 is almost identical effort-wise, so going to it would be preferable)

Thanks!

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi,

Is there a good valid reason not to upgrade to the latest GP build (as the others pointed out) ? effort wise it will be almost as much work anyway to move GP to a new server and test everything, while being behind in SQL & Windows versions, vs. upgrading to the latest versions of everything..

Unless you have some old 3rd-party ISV tools that do not work with the latest GP builds..

Was this reply helpful? Yes No
gary.nease@marketle... 10 on at

Like (0)

Report

1. The link above is broken. I did find docs.microsoft.com/.../mdgp2016_system_requirements.

2. Can I run GP 2016 using SQL 2019 in compatibility level 130?

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

GP 2016 is not compatible with SQL 2019. This links works for me.

docs.microsoft.com/.../MDGP2016_System_Requirements

Was this reply helpful? Yes No
Justin Sutton on at

Like (0)

Report

We just decommissioned CustomerSource and PartnerSource so those links will no longer work. The Docs site should have most of the documentation moved over, although it is a slow process and we are not moving items that are no longer needed (i.e. compatibility of GP 2010 with O365). As noted by Richard, GP 2016 is not compatible with SQL 2019, regardless of compatibility level.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Gary,

is this a temporary move ? is the purpose of installing GP 2016 on SQL 2019 to upgrade to the latest build of GP 18.3 ? if so, there are ways to get around the SQL version limit, but it's not supported, and BTW, GP 2016 will be out of support past 07/2021.

Was this reply helpful? Yes No
gary.nease@marketle... 10 on at

Like (0)

Report

Thanks for your response, Beat.

We have been using GP 2016 on SQL 2012 for quite some time. We are now in the process of upgrading all of our SQL servers to 2019. Our products’ deep integrations with GP mean we avoid upgrading it any more than necessary (only once in my seven years here, AFAIK). The impeding end-of-life of GP 2016 may be such a necessity, but that issue has not been discussed AFAIK.

I would like to know as much as possible about the unsupported "ways to get around the SQL version limit", because my management will make the risk/reward call between that unsupported config vs running SQL 2012 on unsupported version GP 2016 after July EOL (or finding resources to do an urgent GP upgrade project).

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (1)

Report

Ok, I get that.

Why don't proceed with an intermediate upgrade to SQL 2016, which is still supported my Microsoft and and does work with GP 2016 ?

I understand that with some external data integration, it is sometimes not easy to switch and move a GP instance to a new server and that it bears a lot of unknown.

This blog post documents the work-around, but keep in mind that you shouldn't keep your current GP 2016 in a PRODUCTION environment too long, as you're going to loose official support the moment you switch platform, and past 07/2021 it's going to be problem anyway.

Shoot me a PM if you need some help to evaluate how complex your upgrade might be to get to the latest GP 18.3 version.

Was this reply helpful? Yes No
Matthew Arp 90 on at

Like (0)

Report

Could you clarify, are there known issues with SQL 2019 or is it simply untested (unsupported)? We have SQL 2019 with GP21016 installed in our development environment and have not run into any issues so far.

Was this reply helpful? Yes No