Notifications
Announcements
No record found.
Can anyone confirm whether GP version 2015 is compatible with SQL 2016 and Windows Server 2016?
Thanks!
Mike
*This post is locked for comments
The official recommendations for GP 2015 are SQL 2012 or 2014 not 2016.
mbs.microsoft.com/.../MDGP2015_System_Requirements
I want to say yes to both. SQL 2016 includes the new and old versions of the ODBC connection drivers. While Richard pointed to the official documentation Microsoft sometimes doesn't go back to update that information.
yes, it is , up and running
Hi Michael,
My 2 cents:
If you are not using something that's compatible as far as Microsoft's system requirements, you are taking 2 risks:
1. If there is a problem and you have to go to Microsoft for support, it may not be supported.
2. You may run into an issue with things not working in the future. This is especially true for SQL Server versions. If you do some searching online you will find lots of situations where SQL was updated to a version not officially supported for the GP version and that caused the company not to be able to install a service pack or upgrade to a newer GP version until the SQL version was rolled back. Not an easy endeavor from what I understand.
So, if you're going to do this, make sure your company understands and accepts the potential risk of #1 above and that you test anything and everything for #2 above.
yes, it is always official and non-official and Microsoft not knowing its products' compatibilities called saving the *** legally
Syed,
How do you get pass this prompt ?
Thank you
regards,
Joie
As per the System Requirements for Dynamics GP 2015, it is only compatible, and thus supported, on the following SQL versions, 32-bit or 64-bit:
Microsoft SQL Server 2014
-Enterprise, Standard or Express
Microsoft SQL Server 2012
- Enterprise, Standard or Express
While you may be able to install/use Dynamics GP 2015 on different versions of SQL Server, you risk running into the above error when you launch GP Utilities, which actually does do a version check of SQL, and there isn't any way to 'trick' Utilities to get around it.
We frequently see customers put themselves in difficult circumstances because they'll put their Dynamics GP application on a non-supported version of SQL Server, then they find they need to go to a higher build of that version of Dynamics GP in order to upgrade, and cannot do it because of what version of SQL they are on, then they end up having to 'downgrade' their GP databases to a lower version of SQL, in order to then upgrade them.
Despite what may be thought of the System Requirements for Dynamics GP, it isn't worth putting your live/production environment in a non-supported scenario, in my opinion.
Thanks
This has nothing to do with 'legal' matter.. The point is that the GP Utilities tools tests and validates the SQL back-end version before applying a new upgrade.. if the SQL version is not supported, you're stuck with your upgrade and as Victoria pointed out, have to roll-back your SQL version, which is all but easy..
I know that technically GP might certainly work after it is installed and you upgrade your SQL server, it will still work.. the point is : "upgrade" with your next GP service pack or release.
If Microsoft certifies some versions of SQL, it's because those were the version available at the time of release.. you cannot expect them to support a new version of SQL server when it gets released 6, 12 or 18 months after the initial release of GP without releasing a new build compiled to support the new SQL version..
This is all about Microsoft *****ing users.
Had a client running GPv9 that upgraded the server to SQL2008R2, everything was fine, till you needed to run the GP Utilities.
The assine GP Utilities SELECT @@VERSION at startup and refuse to run on unsupported versions
Could not create new companies, install service packs, etc.
Wound up using a perl script to proxy the connection to SQL and replace the version string returned by SQL to the @@AX 2012 version
Worked well when using Utilities, never had any issues with the GP application itself, ran on 2008R2 with no issue for over a year, just not the utilities.
Used the proxy when upgrading to GP2010 and it went well, but not something I'd recommend.
Now I'm stuck upgrading a used from GP2010 to GP2018.
GP2010 won't go beyond SQL2008, GP2015 only supports SQL2012 or SQL2014, Using SQP2016 for GP2018
So I need 3 SQL instances to upgrade one system!
Fine to check for supported versions and warn that there may be issues, but a full stop for no reason is unreasonable.
Hi H. Worby,
Thanks for sharing your option with the perl script to proxy the SQL connection and 'fake' it a lower SQL version than it is :-)...
I disagree with your last statement ",.. GP2010 won't go beyond SQL2008, ...", simply because I just upgraded a customer from GP 2010 SP2 to GP 2018.. and all was done on a Windows 2016 OS server with SQL 2012R2.. the trick is that 2010 SP4 supports SQL 2012.. and all subsequent GP versions up to 2018. So you can upgrade 5 versions (2010-2013-2015-2016-2018) on a single instance of SQL 2012..
No need to install 3 instances of SQL.. unless there is a particular reason to have the latest shiny SQL 2016.. ?
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
