web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Dynamics GP 2016 R2 an...
Microsoft Dynamics GP (Archived)

Dynamics GP 2016 R2 and GP 2018 and SQL Server 2017

(0) ShareShare
ReportReport
Posted on by MattOlson

Can I run GP 2016 R2 with SQL Server 2017? We plan on upgrading to 2017 in a couple of weeks.

System Requirements say no below. Really not sure why I couldn't though? Does GP still do SQL version checks for unnecessary reasons?

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

Can I just set the Dynamics GP databases to SQL 2016 compatibility mode instead or is GP still running select @@version statements for SQL version check purposes? What are those purposes?

System Requirements for the yet to be released GP 2018 also states no compatibility for SQL 2017!?!

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

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    Interestingly enough, I had this same conversation with Microsoft as to why they continue performing SQL Server version checks with the newer releases, but the answer was, "we need to do them". Personally, I believe there's nothing GP does out of the ordinary that would warrant a SQL Server version check. But I can see the other side of that coin, i.e., some customer installing GP on a SQL Server community preview version for example and expecting support if something doesn't go their way.

    While you can set the version compatibility of the databases to SQL 2016, that will not be enough to quiet down Dynamics GP Utilities if you ever decided to setup a new company - yes, and I am implying that is possible to run GP 2016 on SQL Server 2017 if you migrate the databases. Dynamics GP Utilities checks the SQL Server engine version directly, not sure if by running @@version or simply calling the actual SERVERPROPERTY() function, but nonetheless, you will be warned and prevented to continue if it detects the version is one that is not supported.

    As for GP 2018, I've been briefed that it will be supported by RTM time. Keep in mind that the system requirements were written more than 2 months ago and a lot has happened since then.

    Hope this helps.

  • EnriqueGarcia Profile Picture
    EnriqueGarcia 113 on at

    Just tried GP 2018 on SQL 2017 and it installs correctly.

    Screen-Shot-2017_2D00_12_2D00_12-at-3.49.00-PM.jpg

    Curiously, GP version info windows reports server as Windows 2012, when it's actually 2016.

    Screen-Shot-2017_2D00_12_2D00_12-at-3.58.32-PM.jpg

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    The reason why we have SQL Server requirements for  Microsoft Dynamics GP, is because our GP Utilities actually does a version check of SQL and if it isn't a supported version, you'll get an error message.

    For example, we see support cases come in all the time where a customer has put their older Dynamics GP on a newer unsupported version of SQL, which works fine, up until they need to apply a service pack to that version of Dynamics GP in order to upgrade to a newer release of Dynamics GP and they are not able to, because they are on a unsupported SQL version, thus GP Utilities won't work for them.

    At that point, they are stuck because there isn't a way to trick GP Utilities as to what SQL version you're actually on  (the database compatibility level doesn't matter) and you can't restore databases from a newer SQL to an older......

    Not to mention, if your Dynamics GP isn't on a 'supported' version of SQL Server,  you may find yourself not able to get support, so it isn't worth the risk.

    Thanks,

  • MattOlson Profile Picture
    MattOlson on at

    The version check is completely unnecessary. It should be removed from GP.

    You can always set the database compatibility level of your databases back to an acceptable level for GP.

    This check does more harm then it helps.

    Our other 23 applications work just fine with SQL Server 2017 and we had to be held back to gain the benefits that SQL Server 2017 would give us because of one application: Dynamics GP.

    It should be up to me if I want to be in an "unsupported" scenario. 

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    I would enter and/or vote on this as a Product Suggestion:

    PRODUCT SUGGESTION:  Is there an enhancement you’d like to see considered?  Use the link below to voice your opinion.  Every suggestion is read and triaged by the Dynamics GP Development Team.  Or vote on an existing suggestion, as the more votes they get, increases the priority rating on it.

    connect.microsoft.com/dynamicssuggestions

    This is the best, and only way, to let Dynamics GP development know what changes you'd like to have added or removed or changed in future releases of the application.

    Thanks,

  • EnriqueGarcia Profile Picture
    EnriqueGarcia 113 on at

    This installation was not tricked. I simply ran GP Utilities and got no warning.

    Can we assume that the version check accepted SQL 2017 as good?

  • MattOlson Profile Picture
    MattOlson on at

    I believe they still have the version check code still in place. So if you want to upgrade to SQL 2017 you HAVE to upgrade to GP 2018. No word as to wether or not GP 2016 R2 users will be able to apply a service pack to upgrade to SQL 2017.

    FYI, SQL 2017 released on October 19. Users around the world running GP had to wait for GP 2018 to be released in order to gain the benefits of SQL 2017.

  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    I can confirm that GP Utilities is querying the @@Version as I attempted to run the ISV Drop of 2018 (pre-RTM) on SQL 2017 and it wouldn't let go thru .. I traced in the background and there is nothing in the world that you can do to force SQL return a different version (other than hacking the packet that travels thru the network and replace on the fly the value :-) ).

    Enrique Garcia,

    Yes 2017 is good to go.. We got confirmed by Microsoft that GP 2018 would support SQL 2017 by the time RTM would be release (Dec. 1st).. however, the requirement specs haven't been updated on Customer/Partner Source apparently.

  • EnriqueGarcia Profile Picture
    EnriqueGarcia 113 on at

    My test install setup went right thru.

  • MattOlson Profile Picture
    MattOlson on at

    I put in a product suggestion here: connect.microsoft.com/.../remove-the-dynamics-gp-sql-server-version-select-in-dynamics-gp-utilities

    Please everyone vote this one up!

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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans