SQL - SubqueriesWhy does a correlated subquery execute slower than a non-correlated subquery?ABecause it uses more memory than non-correlated subqueriesBBecause it cannot use indexes on the outer queryCBecause it runs once per outer query row, increasing execution timeDBecause it returns multiple rows instead of oneCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand execution frequencyCorrelated subqueries execute once for each row of the outer query, causing repeated work.Step 2: Compare with non-correlated subqueriesNon-correlated subqueries run once, so they are generally faster.Final Answer:Because it runs once per outer query row, increasing execution time -> Option CQuick Check:Repeated execution per row slows correlated subqueries [OK]Quick Trick: Repeated execution per row causes slower correlated subqueries [OK]Common Mistakes:MISTAKESBlaming memory usage instead of execution countAssuming correlated subqueries return multiple rowsThinking indexes are not used
Master "Subqueries" in SQL9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More SQL Quizzes Aggregate Functions - COUNT(*) vs COUNT(column) difference - Quiz 1easy GROUP BY and HAVING - WHERE vs HAVING mental model - Quiz 12easy INNER JOIN - Joining on primary key to foreign key - Quiz 12easy Set Operations - EXCEPT (MINUS) for differences - Quiz 10hard Subqueries - Subquery in FROM clause (derived table) - Quiz 6medium Subqueries - Subquery with EXISTS operator - Quiz 10hard Table Constraints - Composite primary keys - Quiz 1easy Table Relationships - Many-to-many with junction tables - Quiz 7medium Views - CREATE VIEW syntax - Quiz 8hard Views - Why views are needed - Quiz 7medium