Do not attempt to cover the entire set of SELECT or WHERE columns with a large composite index or SQL Server "include columns". Such a solution is expensive in terms of storage costs, ingestion overhead, and statistics run time. Also, future changes might break the solution when either user or system property columns are added to the SELECT list. These changes might occur during Content Platform Engine upgrades, metadata authoring, or changes in the search.
Content Platform Engine SQL | Corresponding database SQL |
---|---|
|
The database SQL contains more WHERE clauses on home_id, object_class_id as well as other system columns such as is_current, depending on the search. |