SQL What I do think tends to make my Prime prepare so poor is that the rows becoming picked from t1 and t2 are several of the latest rows (most significant values for t1.id and t2.id). The query optimiser has assumed that finding the primary 5 rows from an evenly dispersed regular resultset is going to be more quickly compared to the non-Leading te