Skinny Tables Flashcards
What are skinny tables?
Created by Salesforce only, and it contains frequently used fields to help avoid joins. Please note: “Join” in this case means joining the standard and custom fields of an object, not joining between different objects.
Why create a skinny table?
Salesforce maintains other, separate tables at the database level for standard and custom fields. This separation requires a join when a query contains both kinds of fields. A skinny table contains both kinds of fields.
Does Skinny Tables have soft deleted records?
No.
When are skinny tables most useful?
When your tables contain millions of records and you want to improve the performance of read-only operations, such as reports
How can you improve the performance of reports if your object contains millions of records?
Contact Salesforce Customer Support to create a skinny table.
How could a skinny table cause problems?
There’s overhead in maintaining separate tables that hold copies of live data. Using them in an inappropriate context can lead to performance degradation instead of improvement.
On which objects can you create skinny tables?
Custom objects, Account, Contact, Opportunity, Lead and Case
What does skinny tables primarily enhance?
Performance for:
- reports
- list views
- SOQL
Which fields can be included on Skinny tables
- Checkbox
- Date and Date/Time
- Number
- Percent
- Phone
- Picklist (multi-select)
- Text (including text area, and text area long)
- URL
Can skinny tables or skinny indexes include encrypted data?
Yes
Provide an example of how an annual or year-to-date report can be improved using skinny tables
Instead of using a date range like 01/01/18 to 12/31/18, use a skinny table to include a Year field and filter on Year =’2018’
What is the maximum number of columns for a skinny table?
100
Can skinny tables include fields across related objects?
No
Are skinny tables copied to all sandbox environments?
No, only to full sandboxes (as of Summer 2015)
Which fields cannot be included on Skinny tables
Formula Fields
Fields derived from other objects (aka lookup)
Large CLOB fields