Table Index not used in Web Report Studio?

[Madelyn_SAS]

If there is an appropriate index and the SQL optimizer determines that using the index will improve performance, the SQL optimizer uses the index without being told to do so. The optimizer is not 100% correct in every case. Although there are SQL commands that will force the use of an index, you do not have control over the PROC SQL that is automatically generated by the query layer used by Web Report Studio. 

[Dominik4]

Thank you for all that feedback.

Its a pitty that I dont have control over the named strip function. Off course the SQL optimizer does not choose an index if the statement contains a strip function in the where condition.

But I found a some kind of workaround. Predefining the same Filter in Maps does not cause the strip function and so the index is working then.