To enable skinny tables, contact Salesforce customer support. For each object table, Salesforce maintains other, separate tables at the database level for standard and custom fields. This separation ordinarily necessitates a join when a query contains both kinds of fields.
Full Answer
What are skinny tables in Salesforce?
Salesforce can create skinny tables to contain frequently used fields and to avoid joins. This can improve the performance of certain read-only operations. Skinny tables are kept in sync with their source tables when the source tables are modified.
How can a skinny table speed up my queries?
Here is an example of how a skinny table can speed up queries. Instead of using a date range like 01/01/11 to 12/31/11 —which entails an expensive, repeated computation to create an annual or year-to-date report—you can use a skinny table to include a Year field and to filter on Year = '2011'. Skinny tables can contain a maximum of 100 columns.
What are skinny tables and why are they useful?
Skinny tables are most useful with tables containing millions of records to improve the performance of read-only operations, such as reports. Skinny tables aren’t a magic wand to wave at performance problems. There’s overhead in maintaining separate tables that hold copies of live data.
How many columns can a skinny table have?
Skinny tables can contain a maximum of 100 columns. Skinny tables can’t contain fields from other objects. For Full sandboxes: Skinny tables are copied to your Full sandbox orgs. For other types of sandboxes: Skinny tables aren’t copied to your sandbox organizations.
What are Skinny Tables in Salesforce?
A skinny table is a custom table within the Force.com platform that contains a subset of fields from a standard or custom Salesforce object. Force.com has the ability to manage multiple skinny tables if needed and keep them completely transparent.
How Skinny Tables Can Improve Performance
Salesforce creates separate tables for standard fields and custom fields for each object table. The separation of these fields typically requires a join when a query contains both types of fields. A skinny table contains both kinds of fields but does not contain soft-deleted records.
Example for Skinny table
Instead of using a date range like 01/01/21 to 12/31/21—which entails an expensive, repeated computation to create an annual or year-to-date report—you can use a skinny table to include a Year field and to filter on Year = ‘2021’.
Skinny Tables In Salesforce
Your organization is having more then 2 million records for a single object? and you are facing performance issue due to Large data Volumes. Use Skinny table if performance is not good enough even after using custom indexes.
What is the Skinny table?
Salesforce can create skinny tables to contain frequently used fields and to avoid joins. This can improve the performance of certain read-only operations. Skinny tables are kept in sync with their source tables when the source tables are modified.
HOW SKINNY TABLES CAN IMPROVE PERFORMANCE
What are skinny tables? What makes them fast? For each object table that’s visible to you, Salesforce maintains other, separate tables at the database level for standard and custom fields. This separation, which is invisible to customers, ordinarily requires a join when a query contains both kinds of fields.
When to Use?
Skinny tables are most useful with tables containing millions of records. They can be created on custom objects, and on Account, Contact, Opportunity, Lead, and Case objects. In addition, they can enhance performance for reports, list views, and SOQL. The skinny table allows you to reorganize selected columns and rows of data into a separate table
Further Leaning
Amit Chaudhary is Salesforce Application & System Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 17 Salesforce Certificates.
What is Salesforce multitenant architecture?
The Salesforce multitenant architecture makes the underlying data table for custom fields unsuitable for indexing. To overcome this limitation, the platform creates an index table that contains a copy of the data, along with information about the data types.
Does the query optimizer use internal statistics?
All fields in the OR clause must be indexed for any index to be used. For LIKE, the query optimizer does not use its internal statistics table. Instead, it samples up to 100,000 records of actual data to decide whether to use the custom index. Custom indexes can be created on deterministic formula fields.
What Is The Skinny table?
How Skinny Tables Can Improve Performance
- What are skinny tables? What makes them fast? For each object table that’s visible to you, Salesforce maintains other, separate tables at the database level for standard and custom fields. This separation, which is invisible to customers, ordinarily requires a join when a query contains both kinds of fields. A skinny table contains both kinds of fields and also omits soft-deleted reco…
When to use?
- Skinny tables are most useful with tables containing millions of records. They can be created on custom objects, and on Account, Contact, Opportunity, Lead, and Case objects. In addition, they can enhance performance for reports, list views, and SOQL. The skinny table allows you to reorganize selected columns and rows of data into a separate table
Considerations
- Skinny tables can contain a maximum of 100 columns.
- Skinny tables can’t contain fields from other objects.
- Skinny tables are copied to your Full sandbox orgs.
- Skinny tables aren’t copied to your sandbox organizations. To have production skinny tables activated for sandbox types other than Full sandboxes, contact Salesforce Customer Support.