You’re offline. This is a read only version of the page.
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?
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!?!
*This post is locked for comments
It isn't all just about licensing new versions of SQL and forcing customers to upgrade. Often times older versions of SQL that are no longer receiving patches can become vulnerable to exploits. Microsoft should be required to support patch releases for known exploits going back several versions, but being able to play together properly within the supported architectures is certainly within their rights to enforce. We encounter this from time to time, as SQL is often used for many things outside of GP. We try to remain vigilant about staying supported on GP versions and the impact of upgrading systems around GP without taking it forward along with them. It is fairly ugly when it gets to this level and we have to support them despite Microsoft not being able to help.
It all goes back to GP Utilities doing the SQL version check.
As mentioned, Dynamics GP 2016 will most likely install with SQL 2017 fine, but when you launch GP 2016 Utilities to complete the installation, or to apply a hot fix, service pack, year-end update, etc., Utilities will fail on the SQL version check and won't allow you to proceed, and this is what makes SQL 2017 incompatible or not supported with Dynamics GP 2016.
I'm just trying to keep customers from installing Dynamics GP on a non-supported SQL version, then they find out they need to apply a patch to their current GP environment in order to upgrade to a later version of Dynamics GP but cannot because their GP databases are on a non-compatible version of SQL, then they have to find a way to 'downgrade' their databases back to a supported version of SQL.
In regards to Why GP development put the SQL version check into GP Utilities, I can't say for sure, but I'd think most likely it was to do a check to make sure customers were updating SQL versions along with Dynamics GP versions, otherwise we end up with Dynamics GP 10.0 on SQL 2017 or Dynamics GP 2018 on SQL 2005.
Another reason we make recommendations of SQL versions is to attempt to keep customers on a supported version of SQL Server, as there are often times when, even though a SQL version is supported with Dynamics GP, that SQL version is no longer supported by the SQL support team, so the requirements help make customers mindful of their SQL version as well.
Thank you
Quick update........SQL Server 2017 isn't on any of the System Requirements pages for Dynamics GP as we have not finished testing with it, which Development is hoping to have done by the end of January/February, at which time it will be added.
The plan is that SQL 2017 will only be supported for use with Microsoft Dynamics GP 2018 and forward, so it will not be supported with Dynamics GP 2016 or prior.
I just didn't want to have any incorrect information out on these forums.
Thank you.
Yes, if Dynamics GP is not compatible with a SQL version, when you launch GP Utilities, it will immediately give you a SQL version error right after you login to Utilities, so from what you mentioned, Dynamics GP 2018 is fine with SQL 2017, they just haven't updated the System Requirements yet.
Superb news!
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!
My test install setup went right thru.
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 :-) ).
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.
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.
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,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (