{"id":233,"date":"2019-11-01T13:43:25","date_gmt":"2019-11-01T13:43:25","guid":{"rendered":"https:\/\/sdf-docs.mansystems.com\/docs\/acr-rules\/performance\/amount-of-indices\/"},"modified":"2022-02-08T09:32:36","modified_gmt":"2022-02-08T09:32:36","slug":"indexamount","status":"publish","type":"docs","link":"https:\/\/sdf-docs.clevr.com\/?docs=acr-rules\/performance\/indexamount","title":{"rendered":"Entity should have a maximum of N indices"},"content":{"rendered":"\n

The index tables must always be re-ordered\/updated upon creating or changing an attribute that affects the index. Also, the database optimizer needs to pick the right index for a query, so multiple indices increase the chance the optimizer chooses the wrong one. <\/p>\n\n\n\n

When set to 3 for example, this rule finds all entities with more than 3 indices and makes it easy to review if the indices are distinctive and useful. <\/p>\n\n\n\n

Please note that, there is no maximum number of indices advised. It all depends on the amount of mutations to the entity and the available disk space.<\/em><\/p>\n\n\n\n

Noncompliant example:<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n

Additional resources on indices <\/h2>\n\n\n\n