Hi Oleg,
In case a specific column has a value of 0 or 1, LF(Low Fast) index is very useful to retrieve the result rows satisfying with the one out of the two values.
That is, it is effective when the column is used as a predicate in where clause.
In your case, the column Sale_Flag is used for a measure factor in the select list, not as a predicate.
It means you don't have to create LF index on the column.
But, it is applicable only when the column Sale_Flag is used in the select list.
You should also check the characteristic of the column whether it can be used as a predicate.
If then, you have to create the LF index on that column, too.
It doesn't matter you create a HNG index on a column which already has a LF index or HG index.
As you know, those indexes are helpful to get better performance in querying, but it also makes us more cost in space management as well as performance in DMLs against the table.
I also would like you to check another way of utilizing FP(1) byte instead of HNG or LF index.
I think it can show us a satisfiable performance and save lots of costs which mentioned above.
Best Regards
Jerry







