Using additional custom indexes in SQL for custom ItemTypes - any best practice tips?

Hi community,

for a couple of tables I use additional SQL indexes for performance reasons.

I noticed that the SQL ItemType allows us to specify custom indexes too and even contains a few for the most common used ItemTypes. Aras for example typically uses them for versioned ItemTypes like classic Part and CAD.

The Aras SQL ItemType has one big advantage -> it´s a visible item that can be exported. Indexes used directly in the SQL database are less obvious to see for admins. 

I wonder if we should use something similar in our own custom ItemTypes in general. Especially for versioned ItemTypes. Of course SQL indexes are mainly used for performance reasons. There are multiple ways to optimize performance.

But has anyone some tips when custom indexes should be considered by default (!) in the context of Innovator?

@ Aras: Do you have any official recommendations or guidelines regarding SQL indexes?

Many thanks for any hint!

Best regards

Angela