>>It seems pretty clear that Rushmore will use any available index, whether it will speed things up or not. Of course "any available" has to be one (or more) that is relevant to the query at hand.
>
>What evidence do you have for this? I've seen Rushmore reject an available index in a join and create a temp index instead.
>
The fact that an index on DELETED() will always be used (when DELETED is ON) is good enough for me.

>>I've seen temp indexes created too, but don't see the relevance to the issue you've replied to.
>
>What I said. I think you can see this happen if you do the prototypical join with the TasTrade data. Customer to Orders to Line Items to Products.
>
>Tamar