Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Donny Kensmoe]

Hello GPUG Community,
I am interested to know if anyone has experienced issues running GP 18.2 with SQL Server 2019?  We have a few clients running it now with no issues but I’m wondering if anyone has experienced any issues related to using SQL Server 2019.  I am planning an upgrade from GP 2015 R2 to GP 18.2 for a customer and was challenged by a colleague as to whether going to SQL 2019 brings additional risk over going with SQL Server 2017.  Let me know your experiences please. Thank you in advance

——————————
Donny Kensmoe
Senior Consultant
Wipfli
Green Bay WI
——————————

[Steve Erbach]

Hi, ,

Sounds like something to ask , , and !

Regards,????

——————————
“Sparkly” Steve Erbach – Green Bay, WI
Co-Chair, GPUG WI (Green Bay) Chapter
Blog: https://www.gpug.com/blogs/steve-erbach
Twitter: twitter.com/serbach

—————
Excel Webinar List as of 12-Nov-2019
——————————
——————————————-

[David Morinello]

There may be a bit of a gray area there. According to the System Requirements at the time GP 22018R2 released, it supported  up to SQL 2017. The October 2019 GP release supported SQL 2019.

I suspect this is what you need right here.. Although the naming convention has changed 18.2.1013 refers to the artist formerly known as GP 2019

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

Microsoft SQL Server 2019 -Enterprise, Standard or Express (18.2.1013 GP version or later)
Microsoft SQL Server 2017 -Enterprise, Standard or Express   
Microsoft SQL Server 2016 -Enterprise, Standard or Express
Microsoft SQL Server 2014 -Enterprise, Standard or Express

Supported Microsoft SQL Server Collation
1. Dictionary Order Case Insensitive – Sort Order 52
In the SQL Server Management Studio, right -click the SQL Server Name and click Properties: Server Collation = SQL_Latin1_General_CP1_CI_AS

2. Binary – Sort Order 50
In the SQL Server Management Studio, right -click the SQL Server Name and click Properties: Server Collation = Latin1_General_BIN

——————————
David Morinello
Senior Dynamics GP Systems Architect
Ascend Learning, LLC
Leawood KS
——————————
——————————————-

[Donny Kensmoe]

I am clear on the system requirements. No grey area for me. I am asking if anyone ran into an issue related to running GP 18.2.1013 or later with SQL 2019.  Microsoft tested it and deemed them compatible but checking if anyone has run into any issues.

——————————
Donny Kensmoe
Consultant
Wipfli
Green Bay WI
——————————
——————————————-

[Randy Plachinski]

Hey Donny

We have a few clients running SQL Server 2019 with GP2018_2_1036 without any issues.

——————————
Randy Plachinski
Senior Consultant
Heartland Business Systems
Little Chute WI
——————————
——————————————-

[Donny Kensmoe]

Thanks Randy. Appreciate the feedback

——————————
Donny Kensmoe
Senior Consultant
Wipfli
Green Bay WI
——————————
——————————————-

[Kayla Schilling]

Hello,

There were two stored procedures that you needed to fix if you were on 18.2 and used SQL 2019. One was for GL, and the other for AA. Those have been fixed in the February hotfix. https://community.dynamics.com/gp/b/dynamicsgp/posts/microsoft-dynamics-gp-february-2020-hotfix-released

I have come across another stored procedure for SOP with AA and Deferred revenue that will give you an error when trying to post to the GL?: “Conversion failed when converting varchar value to data type int”.

At this time, if a customer is on SQL 2019, I am keeping the compatibility of the databases to 2017 as a workaround until all of the stored procedure kinks with GP 18.2 and SQL 2019 are worked out.  

Regards,
Kayla

——————————
Kayla Schilling
The Resource Group
Renton WA
——————————
——————————————-

[Donny Kensmoe]

Thank you for sharing Kayla. That’s good info.

——————————
Donny Kensmoe
Senior Consultant
Wipfli
Green Bay WI
——————————
——————————————-

[Donny Kensmoe]

Terry Heley sent me one more nugget on this topic in case anyone other than me is paying attention. Thanks Terry!

SQL 2019 Error on 18.2 All Purchasing Transactions Navigation List – Expression services limit has been reached

It is an error you can OK through and the list loads just fine. It will be fixed with the mid-year update.

——————————
Donny Kensmoe
Senior Consultant
Wipfli
Green Bay WI
——————————
——————————————-