Create Index in DB for attribute on a large/complex entity for improved performance and searching

Who would benefit?

Anyone who has a large number of instances of an entity/complex search requirements on an entity in InRiver.

What impact would it make?

Speed up reads of complex/large tables in the DB and improve search functionality/speed.

How should it work?

When you add or edit an attribute on an entity in the control center, there should be a field called DB Index that would make that particular column in the DB have an Index. This would be like the Unique field on an attribute where it creates an index for that attribute, but would allow non unique fields to have indexes.

Why is it needed?

Customer's with a large number of instances of an entity and/or complex search requirements on entities and in data models tend to have performance issues or slowness while doing searches in the data model and can benefit from being able to mark fields that they would search upon to create an Index to speed up this process.