Guidelines for creating indexes
You determine what constitutes the optimal set of database
indexes for your system and needs. The benefits of faster queries
must be weighed against the performance costs that database indexes
impose for object creation and object updates.
Necessary indexes Unnecessary indexes Unnecessary indexes for system properties Content Platform Engine to the database SQL query. Most system columns that require indexes are already indexed automatically when an object store is created.Not every property needs to be indexed 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.Complex query experimentation