I just started to play with an SQL optimizer tool. If it creates a "better" SQL Statement than the DR studio does, is there a way to force DR to use the better query, or am I tied only to the "native" query?

What are the mechanisms to 'encourage' the studio to make better choices?

Also, so far all the queries have been nested inner joins, and DR's version has been just peachy.