Suggestion: Added indexes to Octopus DB should result in warnings and not errors in the System Integrity Check

We, like many, have added indexes to our Octopus DB in order to improve the performance of certain queries. Since upgrading from 3.2 to 3.11 we now have the System Integrity check which is awesome. But since we’ve added the indexes the schema does not map to the OOTB one creating errors. The check will always fail meaning I might miss something important. I suggest the unexpected items should be logged as warnings and not errors, thus not failing the check.

Hi Erik,

The reason we have currently decided to make even index differences an error is that extra indexes are a major cause we run into of failed upgrades. We try to make a change to a column as part of an upgrade and that fails because the customer has additional indexes referencing the column.