Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
on sql Server you can use different compatiblity levels to support legacy applications.
e.g If an application supports SQL Server 2016 you can run SQL Server 2017 with Database Level 130.
From this view I see the possibility that you can run SQL Server 2017 and the crm Databases with Level 130.
Is this possible?
Thanks in advance.
Hope you are well.
According to support.microsoft.com/.../compatibility-with-microsoft-dynamics-crm-2016, CRM 2016 does not support SQL 2017. Ignoring for now the SQL 2017 compatiblity, if you want to use CRM with compatiblity 130, we suggest you to enable legacy cardinality estimation as Product Group decided to install v9 vanilla orgs with compatiblity 130, but with legacy cardinality estimation, as per the current understanding is that without the previous setting, compatiblity 130 may have some bottlenecks.
Any doubt, let us know.
sorry for the delay.
thanks for your explanation.
Business Applications communities