Not necessarily. SCAN is Rushmore optimizable with a FOR clause if you have an index on what you are scanning for. So just because you have removed the order on the table, rushmore should still use the index to scan.

>So, would you suggest me to switch? I believe I solved the problem by removing order, but I'm not certain...