Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All 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