Capture EXPLAIN before and after your next real tuning change on one named slow query. This fits a dashboard query, warehouse model, ETL statement, or API endpoint SQL where you can identify a concrete symptom such as a large sort, unrealistic row estimate, or missing ordered access path. For the [query name] query, I will capture EXPLAIN before the change, make [index / rewrite / stats] change, then capture EXPLAIN again and compare [specific symptom] such as row estimate accuracy, sort size, or ordered index usage. In 2 days, verify whether you captured both plans and whether the expected node…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in