-
Notifications
You must be signed in to change notification settings - Fork 28
16) Large Data Volume Notes
Typically anytime you see an object that will hit or exceed 1 million records it should be pointed out as an LDV object. Salesforce has a recommendation of no more than 50 million records per object, so when you see an object has or very likely will hit 50 million records you absolutely need to provide a way to offload/archive that data.
NOTE: If you have LDV on the Contact and/or Account object and those records are associated with an experience cloud user I would NOT suggest archiving them. Instead I would state that you would monitor them and look out for any account or ownership skew, and any performance slowdowns due to the large volume, and leverage custom indices and skinny tables to deal with any slowdowns should they occur. Archiving a contact related to a user is a dangerous road to go down unless it's absolutely mandatory.
Skinny tables are a mechanism you can deploy to speed up read only operations on tables with millions of records. For instance, if your contact object has 100 million records in it, and you notice that reports and list views are loading slower due to that volume, you can contact Salesforce support to setup a skinny table for your object to improve your performance in those read only areas.
There are drawbacks to skinny tables however, for instance, if you add a new field to your object and you add that to your list views, reports, etc, your skinny table will not be automatically updated to include that field, you must contact SF Support to have them manually add that new field to the skinny table.
Additionally Skinny Tables can only be used on the following objects:
- Account
- Contact
- Opportunity
- Lead
- Case
- Custom Objects
And skinny tables can only contain the following field types:
- Checkbox
- Date
- Date and time
- Number
- Percent
- Phone
- Picklist (multi-select)
- Text
- Text area
- Text area (long)
- URL