Designing Record Access for Enterprise Scale

Designing Record Access for Enterprise Scale
Preface
Introduction
Group Membership Operations and Sharing Recalculation
Object Relationships, Bulk Loading, and Sharing Recalculation
Implicit Sharing
Parent-Child Data Skew
Record-Level Locking
Takeaway: Tuning Data Relationships and Updates for Performance
Tools for Large-Scale Realignments
Conclusion
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Takeaway: Tuning Data Relationships and Updates for Performance

Understand the performance characteristics of the various maintenance operations that you are performing and always test substantial data uploads and changes to object relationships in a sandbox environment so you know what to expect.

Here are some specific suggestions.
  • Use a Public Read Only or Read/Write organization-wide default sharing model for all non-confidential data.
  • To avoid creating implicit shares, configure child objects to be Controlled by Parent wherever this configuration meets security requirements.
  • Configure parent-child relationships with no more than 10,000 children to one parent record.
  • If you are encountering only occasional locking errors, see if the addition of retry logic is sufficient to solve the problem.
  • Sequence operations on parent and child objects by ParentID and ensure that different threads are operating on unique sets of records.
  • Tune your updates for maximum throughput by working with batch sizes, timeout values, the Bulk API, and other performance-optimizing techniques.