... or is that a little too far out on the bleeding edge?
*This post is locked for comments
Dear BrainMan;
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.
So it is possible to run GP 2016 on SQL Server 2017 if you migrate the databases.
but since GP Utilities does an SQL version check (which is only necessary to prevent running older SQL Server versions, not newer ones!!!), an SQL version error message will appear and Utilities won't run... so you can not setup new companies, or apply a hot fix, service pack, year-end update... until you "downgrade" the SQL Server.
Best Regards;
Ibrahim
please verify my reply as an answer if it helped you.
Ibrahim is right.
I wouldn't bet my Production systems on an unsupported SQL platform..
Read on about the details here:
community.dynamics.com/.../259775
Thank you for your reply...
Thank you for your reply, and your contributions on your linked post.
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 Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
