I am aware of the concept of ownership skew (https://developer.salesforce.com/blogs/engineering/2012/06/architect-salesforce-record-ownership-skew-for-peak-performance-in-large-data-volume-environments.html), but is this also a problem for a parent - child relationship outside the concept of owning a record?

A more specific example is I am looking at entitlements and currently every Case/Contact would be associated to the same entitlement. Would this cause any issues over time?


That would be a slightly different problem, that article refers to ownership skew and you are referring to a data skew, which is what would happen when you have a large number of child records related to the same parent record, this issue happens more often around accounts but I guess it can happen in most master-child relationships.



  • Thanks those links are helpful. So in theory as EntitlementId on EntitlementContact appears to be a master detail lookup to Entitlement we could hit performance issues at around 10K EntitlementContact records? – Girbot May 13 '15 at 13:26
  • I think is technically possible but I wouldn't be concerned about those two particular objects because updating them doesn't have a big impact (or any?? ) on sharing across multiple other records, which is the case with other objects such as accounts or users. – PepeFloyd May 13 '15 at 13:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.