Secondary indexes - response (13) by vrushang

Knowing that tables are loaded with mload so there won’t be any join index so  SI would help to join tables .
I agree with Shelley. Creating a  valued order NUSI would be good, when you are running small range queries and USI when equality conditions when SI columns is part of where clause.
If there are multiple SI then avoid using OR operator as optimizer would not consider the SI and perform FTS. So for optimizer to SI use the AND operator ( NUSI Bit mapping)
Cons of SI
1)if stats not collected on the SI columns then it won’t be effective.
2) SI would need additional IO , thus if MLOAD is updating  the SI column it might be costly to create SI