Dinesh Kumar’s Post

🚀 Day 2/30 — SQL + Python Deep Dive Subqueries (Correlated vs Non-Correlated) 👉 Basics are done. Pipelines are built. 👉 Now we go deeper — into how SQL really executes and how Python scales. You’ve used subqueries before… But do you know: 👉 how they actually run? 👉 why some are slow? 🔹 What is a Subquery? 👉 A query inside another query 🔹 1. Non-Correlated Subquery 👉 Runs once, result is reused SELECT name FROM employees WHERE salary > ( SELECT AVG(salary) FROM employees ); 👉 Inner query runs once → outer query uses result 🔹 2. Correlated Subquery 👉 Runs for each row of outer query SELECT name FROM employees e1 WHERE salary > ( SELECT AVG(salary) FROM employees e2 WHERE e1.department = e2.department ); 👉 Inner query runs again & again 😐 🔹 Key Difference Non-correlated → runs once ⚡ Correlated → runs per row 🐢 🔹 Why This Matters Big impact on performance Correlated queries can be slow Often replaced using JOIN or CTE 🔹 Real Insight 👉 If your query is slow… 👉 check if it’s a correlated subquery 💡 Quick Summary Subqueries are powerful… But execution matters more than syntax 💡 Something to remember Same logic… Different execution → different performance. #SQL #Python #DataEngineering #LearningInPublic #TechLearning

  • No alternative text description for this image

To view or add a comment, sign in

Explore content categories