Universal Containers (UC) has an Application custom object, which has tens of millions of records created in the past 5 years. UC needs the last 5 years of data to exist in Salesforce at all times for reporting and queries. UC is currently encountering performance issues when reporting and running queries on this Object using date ranges as filters. Which two options can be used to improve report performance?
A.
Ask support to create a skinny table for Application with the necessary reporting fields.
B.
Add custom indexes to all fields on Application without a standard index.
C.
Run multiple reports to get different pieces of the data and combine them.
D.
Add custom indexes to the Date fields used for filtering the report.
A.
Ask support to create a skinny table for Application with the necessary reporting fields.
D.
Add custom indexes to the Date fields used for filtering the report.
Explanation:
A (Skinny table): Salesforce skinny tables dramatically improve query/reporting performance by providing a condensed, indexed version of heavily queried tables for faster access.
D (Custom indexes on date fields): Custom indexing critical filter fields (such as date ranges) significantly enhances query speed by optimizing search and filtering.
Indexing every field (Option B) unnecessarily burdens system resources and storage. Running multiple reports (Option C) creates complexity without directly addressing underlying performance inefficiencies. Skinny tables plus targeted custom indexing is the optimal Salesforce-recommended strategy.