4 SQL Best Practices for Cleaner Code

SQL Journey – Day 27: Subqueries Deep Dive (Advanced Practice) Today’s focus: Understanding how subqueries work internally and how to use them effectively for real-world problem solving. This was not just theory — practiced multiple scenarios to understand execution flow and logic building. ⸻ 🔹 What I Explored Subqueries inside SELECT, WHERE: • Using subqueries to fetch intermediate results • Comparing values using nested queries • Writing conditions based on dynamic results ⸻ 🔹 Types of Subqueries Practiced ✅ Single Row Subquery • Returns one value • Used with operators (=, >, <, etc.) ✅ Multi Row Subquery • Returns multiple values • Used with IN, ANY, ALL • Executes row by row ✅ Correlated Subquery • Depends on outer query • Executes row by row ⸻ 🔹 Key Concepts Understood • Subqueries execute inside → outside • Outer query depends on inner query results • Must maintain data type compatibility • Can be nested multiple levels ⸻ 🔹 Real Practice Scenarios • Example: Finding average value using subquery • Correlated subqueries are powerful but expensive • Poor usage can impact performance • Sometimes JOINs are a better alternative ⸻ 💡 Day 27 Realization • Subqueries are not just a concept — they are a thinking pattern • They help break complex problems into smaller logical steps • Mastering them = writing smarter SQL, not longer SQL ⸻ 🔖 Hashtags #SQL #Subqueries #AdvancedSQL #DataAnalytics #LearningJourney #RDBMS #TechCSE

🚀 𝗦𝗤𝗟 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 – 𝗗𝗮𝘆 𝟮𝟲 & 𝟮𝟳: 𝗠𝗮𝘀𝘁𝗲𝗿𝗶𝗻𝗴 𝗦𝘂𝗯𝗾𝘂𝗲𝗿𝗶𝗲𝘀 🔍 Over the past two days, I explored one of the most powerful and practical concepts in SQL — Subqueries. 🔹 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝗦𝘂𝗯𝗾𝘂𝗲𝗿𝗶𝗲𝘀? Subqueries are queries written inside another query, helping break down complex problems into simpler, logical steps. --- 💼 𝗥𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀: Used to answer business-critical questions like: ✔️ Which customers are spending above average? ✔️ Which products or stores are performing best? --- 🔹 𝗞𝗲𝘆 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗟𝗲𝗮𝗿𝗻𝗲𝗱: 📌 𝗖𝗼𝗿𝗿𝗲𝗹𝗮𝘁𝗲𝗱 𝗦𝘂𝗯𝗾𝘂𝗲𝗿𝗶𝗲𝘀 ➡️ Inner query depends on outer query ➡️ Executes for each row 📌 Types based on Result: • 𝗦𝗰𝗮𝗹𝗮𝗿 → Single value • 𝗥𝗼𝘄 → Single row, multiple columns • 𝗧𝗮𝗯𝗹𝗲 → Multiple rows & columns 📌 Types based on Usage: • 𝗪𝗛𝗘𝗥𝗘 clause • 𝗦𝗘𝗟𝗘𝗖𝗧 clause • 𝗙𝗥𝗢𝗠 clause 📌 Common Keywords: IN | EXISTS | ANY | ALL --- 💻 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀: ✔️ Found customers spending more than average ✔️ Compared grouped data dynamically ✔️ Improved understanding of query optimization --- 🧠 𝗠𝘆 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀: ✨ Subqueries simplify complex logic ✨ They make queries more dynamic and powerful ✨ Choosing the right type improves performance --- 📈 𝗣𝗿𝗼𝗴𝗿𝗲𝘀𝘀: Step by step, getting more confident in writing efficient SQL queries and solving real-world problems. #SQL #Subqueries #DataAnalytics #LearningJourney #40DaysOfCode #Database #StudentDeveloper

🚀Day 85 of My 100 Days Data Analysis Journey What makes this kind of resource powerful for beginners is simple... It doesn’t just teach SQL commands, it shows how everything connects. If SQL ever felt overwhelming… it’s not because it’s complex, it’s because it wasn’t structured properly. That’s why resources like a well-organized SQL cheat sheet change everything. Instead of scattered syntax, it brings clarity to what actually matters: 🔹 Core Query Structure Understanding how SELECT, FROM, and WHERE work together, the true foundation of every query. 🔹 Filtering & Conditions Using operators, LIKE, BETWEEN, and logical conditions to refine data with precision. 🔹 Sorting & Limiting Results ORDER BY and LIMIT, simple, but essential for making outputs meaningful. 🔹 Aggregations & Grouping COUNT, SUM, AVG, paired with GROUP BY and HAVING; turning raw data into insights. 🔹 Joins & Relationships INNER, LEFT, RIGHT JOIN; where SQL moves from single tables to real-world data connections. 🔹 DDL vs DML Understanding the difference between structuring data (CREATE, ALTER) and working with it (SELECT, INSERT, UPDATE, DELETE). And once that connection clicks, SQL becomes less about memorizing… and more about thinking clearly with data. If you find this helpful, kindly repost to share this with others. #SQL #DataAnalytics #LearningInPublic #DataSkills #TechJourney #100DaysOfCode #Databases

🚀 SQL Journey – Day 26 to Day 28: Deep Dive into Subqueries Over the last three days, I explored one of the most powerful and widely used SQL concepts - Subqueries. These concepts helped me understand how to break complex problems into simpler, logical steps. 🔹 Day 26 – Introduction to Subqueries A subquery is a query inside another query used for intermediate calculations and filtering. 💼 Real-world perspective: • Which product performs well? • Which store performs well? • Which customers perform well? 👉 Subqueries help answer these by comparing values with averages or totals. ✔ Learned about: • Correlated Subqueries (row-wise execution) • Non-correlated Subqueries (single execution) 🔹 Day 27 – Types of Subqueries (Based on Result Type) • Scalar Subquery → Returns single value • Row Subquery → Returns one row, multiple columns • Table Subquery → Returns multiple rows & columns 💡 Practice focus: ✔ Customers spending above average ✔ Filtering & counting results dynamically 🔹 Day 28 – Correlated vs Non-Correlated Subqueries • Correlated Subquery → Depends on outer query → Executes for each row → Used for detailed comparisons • Non-Correlated Subquery → Independent → Executes once → Faster and efficient 📊 Key Learnings: ✔ Breaking complex queries into smaller steps ✔ Dynamic filtering using subqueries ✔ Choosing the right type improves performance ✔ Strong foundation for real-world analytics 💡 Key Takeaway: Subqueries are essential for solving real-world business problems, especially when dealing with comparisons, filtering, and analytical queries. 🔥 Consistency + Practice = Mastery in SQL #SQL #DataAnalytics #LearningJourney #Subqueries #SQLPractice #Database #TechLearning #30DaysOfSQL #AIStudent 🚀

📘 SQL Journey – Day 28: Mastering Subqueries (Types & Practical Clarity) Today’s focus was on strengthening my understanding of different types of subqueries and when to use each in real-world scenarios. Instead of just writing queries, I focused on choosing the right type of subquery for the problem. ⸻ 🔹 Types of Subqueries (Deep Understanding) ✅ Single Row Subquery • Returns only one value • Used with operators (=, >, <, >=, <=) • Example use: Compare salary with average salary ✅ Multi Row Subquery • Returns multiple values • Example use: Filter records based on multiple matching values ✅ Correlated Subquery • Depends on outer query → Executes once for each row • Used for row-wise comparisons • More powerful but can impact performance if not optimized ⸻ 🔹 Key Learning Shift ✔ Earlier: “Write a subquery” ✔ Now: “Which subquery type fits this problem?” • That’s the real difference ⸻ 🔹 Important Rules ✔ Subquery executes inside → outside ✔ Data types must match between inner & outer query ✔ Correlated subqueries run multiple times ✔ Can be used in SELECT, WHERE, FROM ⸻ 🔹 Real Use Cases Practiced • Employees earning above department average • Filtering based on dynamic conditions • Replacing row values with aggregated results • Replacing complex joins with subqueries (and vice versa) ⸻ 💡 Day 28 Realization Choosing the right approach (JOIN vs Subquery) That’s what makes you strong. That’s where real problem-solving begins. ⸻ #SQL #Subqueries #AdvancedSQL #DataAnalytics #LearningJourney #RDBMS #HappyToCode

🚀 SQL Journey – Day 32: Recursive CTE (Hierarchical Queries) Today’s focus was on Recursive CTEs, one of the most powerful SQL concepts used to work with hierarchical or repeating data. 🔹 What is a Recursive CTE? A Recursive CTE is a CTE that calls itself repeatedly to process hierarchical or sequential data. 👉 Used when data has parent-child relationships 🔹 Basic Structure WITH cte_name AS (  -- Anchor Query (starting point)  SELECT ...  UNION ALL  -- Recursive Query (calls itself)  SELECT ...  FROM table t  JOIN cte_name c ON condition ) SELECT * FROM cte_name; 🔹 Key Components ✔ Anchor Query → Starting rows ✔ Recursive Query → Repeats logic ✔ UNION ALL → Combines results ✔ Stops when no new rows are returned 🔹 Where is it Used? • Employee → Manager hierarchy • Category → Subcategory structure • Organizational charts • Tree-like data traversal 🔹 Concept Understanding (From Today’s Notes) Recursive CTE works step-by-step: 1️⃣ Start with base data (Anchor) 2️⃣ Use result to fetch next level 3️⃣ Repeat until condition fails 👉 Like traversing a tree or graph 🔹 Important Rules • Must use UNION ALL (not UNION) • Recursive part must reference CTE name • Be careful with infinite loops • Can control depth using conditions 🔹 Interview Insight 💡 If a problem involves: • Hierarchy • Levels • Parent-child relationships 👉 Think Recursive CTE immediately 💡 Day 32 Realization Recursive CTE is not just SQL — it’s logic + iteration inside queries. Once you understand this, you can solve complex hierarchical problems easily. SQL is getting deeper. Thinking is getting sharper. HAPPY LEARNING!✨ #SQL #CTE #RecursiveCTE #DataAnalytics #LearningJourney #SQLPractice #RDBMS #TechJourney #CSE

SQL Optimization isn't about writing less code. It's about understanding what happens AFTER you hit run. Most engineers I know can write SQL. Very few understand what it costs. Here's everything that actually matters: 1. The Query Optimizer isn't magic It builds an execution plan based on statistics. Old or missing statistics = bad plan = slow query. Update your stats. Trust the plan less. 2. SARGability is everything SARG = Search ARGument Able. If your filter can't use an index, it scans the whole table. This breaks SARGability: WHERE YEAR(created_at) = 2024 This doesn't: WHERE created_at >= '2024-01-01' AND created_at < '2025-01-01' Same result. Completely different cost. 3. Implicit conversions are silent killers ISNULL(Amount, 0) when Amount is decimal? The engine converts everything to int quietly. Your index? Ignored. 4. Execution Plans > Gut Feeling Before optimizing anything read the plan. Look for: Table Scans, Key Lookups, Sort operators. These are your cost red flags. 5. Indexes aren't free Every index you add speeds up reads. But slows down writes. Design for your actual workload. The real lesson? Writing SQL is a skill. Understanding SQL cost is a discipline. One gets the query working. The other keeps the system alive at 3AM. Which of these did nobody teach you formally?👇 Found Insightful? ♻️ Repost in your network and follow Sahil Alam for more. #SQL #DataEngineering #Analytics #Debugging #DataQuality #Learning

🚀 SQL Roadmap: From Beginner to Advanced 📊 Want to master SQL step-by-step? Here’s a clean, structured roadmap to guide your journey 👇 🔰 1. Basics 📌 Understand what SQL is 📌 Learn Databases & Tables 📌 Master CRUD operations (Create, Read, Update, Delete) 📌 Get familiar with DDL & DML 📊 2. Queries ✨ SELECT, WHERE (AND/OR/NOT) ✨ ORDER BY, GROUP BY ✨ LIMIT & DISTINCT ⚙️ 3. Functions 🔢 Aggregate: COUNT, SUM, AVG, MIN, MAX 🔤 String: UPPER, LOWER, CONCAT 📅 Date: NOW, DATE, DATEDIFF 🧩 NULL handling with COALESCE 🔄 4. Joins 🔗 INNER JOIN 🔗 LEFT & RIGHT JOIN 🔗 FULL JOIN 🔗 SELF & CROSS JOIN 🧠 5. Subqueries 📍 Subqueries in SELECT, FROM, WHERE 📍 Correlated subqueries 🚀 6. Constraints 🔒 PRIMARY KEY, FOREIGN KEY 🔒 UNIQUE, NOT NULL 🔒 CHECK & DEFAULT ⚡ 7. Indexes & Views 📈 Indexing for performance ⚖️ Index trade-offs 👁️ Creating & using views 🔁 8. Normalization 📚 1NF, 2NF, 3NF 📉 Reduce redundancy ⚖️ When to denormalize 🔐 9. Transactions 💾 BEGIN, COMMIT, ROLLBACK 🛡️ ACID properties ⚙️ Isolation levels 🔥 10. Advanced SQL 💡 Window Functions 💡 Common Table Expressions (CTEs) 💡 Stored Procedures & Triggers 🎯 11. Practice & Next Steps 🛠️ Build real-world projects 🎤 Prepare for interviews ⚡ Practice query optimization 💬 Consistency + Practice = SQL Mastery! #SQL #DataAnalytics #DataScience #Learning #TechSkills #Programming #DataEngineering #Database #LearningPath

Stop writing SQL for the database engine. Start writing it for the human who has to maintain it (probably you). We’ve all inherited that query. You know the one: 1,000 lines of monolithic code, nested subqueries seven levels deep, and zero comments. It runs, but modifying it feels like playing Jenga with production data. The engine doesn't care about your messy code, but your team's agility does. The shift every Data Analyst needs to make is toward Modular SQL. Modular code is readable code. Readable code is enhanceable code. Here is the blueprint for SQL that survives schema changes and business logic updates: ✅ DO: 1. Use CTEs (Common Table Expressions) to break complex logic into isolated steps. 2. Select explicit columns, never SELECT * in production. 3. Leverage Window Functions over messy self-joins. 4. Comment on WHY the logic exists, not how it works. ❌ DON'T: 1. Nest subqueries deeper than three levels. (Convert them to CTEs!) 2. Use SELECT * (protect your query from table schema evolution). 3. Perform raw date manipulation in WHERE clauses (isolate it in a CTE). 4. Adopt modular SQL. Save future-you hours of debugging. Less firefighting = More analysis. Check out the cheat sheet below. What’s the worst SQL anti-pattern you've encountered in code review? Share your pain below. 👇 #SQL #DataAnalytics #DataEngineering #CodingBestPractices #Analytics #DataScience #CareerGrowth

🚀 The SQL Roadmap: From Zero to Expert To truly master SQL, you must progress through these core layers: • The Foundation: Understand DDL (Data Definition) for managing structures like tables and DML (Data Manipulation) for handling the data itself. • Querying & Filtering: Mastering SELECT, WHERE, and logical operators like AND/OR to extract exactly what you need. • Aggregations & Grouping: Using functions like SUM(), AVG(), and COUNT() with GROUP BY to generate summary statistics. • Advanced Joins: Moving beyond INNER JOIN to master LEFT, RIGHT, and FULL OUTER joins for complex data relationships. 💡 Pro-Level Concepts to Ace Your Interview If you want to stand out, focus on these advanced topics often asked by top tech companies: • Window Functions: Commands like RANK(), DENSE_RANK(), and LEAD/LAG allow for powerful calculations across rows without collapsing your data. • CTEs vs. Subqueries: Common Table Expressions (CTEs) are often more readable and efficient for complex, multi-step queries. • Performance Optimization: Understanding Indexes (Clustered vs. Non-Clustered) to speed up data retrieval. 🧠 Can You Answer These? Interviewers love "Conceptual" questions to test your depth. Do you know the difference between: WHERE vs. HAVING? (Row-level vs. Aggregate filtering). DELETE vs. TRUNCATE? (Logged row removal vs. fast table clearing). UNION vs. UNION ALL? (Removing duplicates vs. keeping them for speed). 🛠️ Practice Resources Knowledge is nothing without practice. Check out these platforms: Beginner: W3Schools, SQLBolt, SQLZoo. Intermediate/Expert: LeetCode (Top 50 SQL Plan), DataLemur, and HackerRank. SQL isn't just about writing code; it's about solving problems and uncovering insights. What SQL concept took you the longest to "click"? Let’s discuss in the comments! 👇 👉 Follow: Dinesh Sahu #SQL #DataScience #DataEngineering #InterviewPrep #TechCareers #DatabaseManagement #CareerGrowth