What does LDV stand for - Large data volumes.
A simplistic rule of thumb is any table over 2 million records
In the context of LDV design what can Heroku be used for - To bring external data from
outside salesforce
W
...
What does LDV stand for - Large data volumes.
A simplistic rule of thumb is any table over 2 million records
In the context of LDV design what can Heroku be used for - To bring external data from
outside salesforce
What are the 4 phases when figuring out an LDV approach - 1. Design - Get to know
the application. Get data volumes. Understand data growth.
2. Load - Use Bulk API to reduce load times.
3. Sharing - The record sharing in SF will have a huge impact on LDV performance.
4. Maintenance - strategy concerning custom indexing; partitioning; app partitioning (so
things like use of external data)
What standard fields are automatically indexed - Id
Name
OwnerId
CreatedDate
SystemModstamp
RecordType (if present on the object)
Email (for contacts and leads)
Master-Detail Fields (treated as custom index)
Lookup Fields (treated as custom index)
What custom fields are automatically indexed - Unique fields
External ID Fields
What are the selectivity conditions for a standard index when it's the only filter term - 1.
30% of the first million
2. 15% after the first million
3. 1 million total records
What are the selectivity conditions for a custom index when it's the only filter term - 1.
10% of first million2. 5% after the first million
3. 333333 total records
What are the selectivity conditions when we use AND in the query - 1. Twice the index
selectivity thresholds for each filter
2. The index selectivity thresholds of the intersection of the fields
3. This is termed as using a composite index
With regards to a date or number range; will the optimiser consider this as one or two
filter terms - One
What are the selectivity conditions when we use OR in the query - 1.The index
selectivity thresholds for each filter
2. The index selectivity thresholds for the sum of those fields
3. This is termed as an index union
What are the selectivity conditions we use LIKE in the query - If we don't start with a
leading wildcard force.com will test the first 100K rows for selectivity
For a standard index what is the maximum number of rows that can be returned by a
filter in order for it to be considered selective - 1 million
For a custom index what is the maximum number of rows that can be returned by a filter
in order for it to be considered selective - 333333
Will a filter be considered selective when it contains any of the following operators : != ;
NOT LIKE ; EXCLUDES - No
Will an filter be considered selective when it pairs a text field with any of the following
operators : < ; > ; <= ; >= - No
Will a filter be considered selective when it starts with a leading wildcard - No
Will an filter be considered selective when it references a non deterministic formula field
- No
Are chatter feed SOSL searches affected by the scope of the search - No - the results
will match across all objects
[Show More]