Personalized Community is here!
Quickly customize your community to find the content you seek.
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 1Discover 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 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
Just wanting to get everyones view on some of the out of the box entity indexing, and if its recommended to change them.
One index in particular is the clustered index on the ListMemberBase table. This index is on ListId, EntityId. Our marketing lists contain 10,000+ contact members, and they are constantly rebuilt via workflows (which run async) which becomes very expensive as every addition to the list incurs a heavy index insert as the enityid guid (listid is less of an issue as there is not nearly as many) needs to be added in the correct order. In this instance, perhaps having the clustered index on listid only would make more sense, and then have another non-clustered index on listid and entityid.
I would suggest you ask this question in the SQL Server forum as well.
My question is more about if changing one of the default clustered index on one of the 'out of the box' entities going to cause any issues with support from MS going forward (ie upgrades etc etc).
Business Applications communities