@spurusothamanusually we go through a couple of steps to troubleshoot issues like this. The two most likely solutions are: 1. Give the query more memory by increasing mem_limit or reducing # of concurrent queries 2. Adjust the SQL by rewriting the query or adding hints to get a different query plan to that avoids having so many duplicate values on the right side of the join. Depending on the exact scenario, the solution might be 1, 2, or both. straight_join is only useful if you use it to force a plan with a different join order. If you want input on whether you have a bad plan and what a better join order might be, please provide a query profile.
... View more
