Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

Database Compatibility Level on SQL2017

(0) ShareShare
ReportReport
Posted on by 202

we upgraded to GP2018, and also upgraded from SQL2014 to SQL2017 (version 14.0.3335.7)

the DYNAMICS and COMPANY DB compatibility level are now set as SQL Server 2014 (120)

should I just keep it as it is or change to 

SQL Server 2016 (130)

SQL Server 2017 (140)

thanks.

Categories:
  • Suggested answer
    Derek Albaugh Profile Picture
    on at
    RE: Database Compatibility Level on SQL2017

    We recommend setting the compatibility level of the database to be that of the SQL version unless there is a reason to do differently, which isn't that common.

    I did hear it mentioned that with SQL 2014 there was a performance issue where changing to SQL 2012 helped resolve it, but other than that, nothing from the Dynamics GP side.

    Thanks

  • Richard Wheeler Profile Picture
    75,848 Moderator on at
    RE: Database Compatibility Level on SQL2017

    I always set the compatibility level to the version of SQL running. However, I have never seen this addressed  so it will be interesting to see what ansewrs come back on this.

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Product updates

Dynamics 365 release plans