Summary
We’ve just completed our dive into the realm of Salesforce and OmniStudio data issues, looking at common causes of non-selective queries and data skew. We now know why the same DataRaptor may perform differently depending on the data. We saw how Salesforce differs from traditional databases and why its indexes are not always used. We then saw how to use the Query Plan tool to keep our queries selective, staying clear of full table scans as much as possible to allow us to keep our queries and our DataRaptors performing at their best—even when our data volumes are growing.
We then looked at data skew issues, locking and performance issues they may cause, and how to avoid them.
In the next chapter, we will look at other causes of sub-standard performance in OmniStudio DataRaptors and Integration Procedures and the best ways to resolve them.
