SQL JOIN Types: LEFT, RIGHT, INNER Explained

Learning Data Analytics the Right Way Series - Ep. 43 SQL for Data Analysis | Types of SQL JOIN Cont'd 🟢 We are wrapping up SQL JOINs today, and these last two types are fascinating. Meet the FULL JOIN and the CROSS JOIN. 1️⃣ FULL JOIN A FULL JOIN retrieves all records from both tables, regardless of whether they match. When there is no match, NULL fills in the gaps. Syntax: SELECT customers_name, orders_order_id FROM customers FULL JOIN orders ON customers.customer_id = orders.customer_id; This returns every customer and every order. No record from either table is left out. Use this when you need a complete picture of both tables together. 2️⃣ CROSS JOIN A CROSS JOIN combines every row from the first table with every row from the second table. No join condition is needed. Syntax: SELECT customers.name, products.product_name FROM customers CROSS JOIN products; If you have 10 customers and 5 products, this returns 50 rows. Every possible combination. It sounds excessive, but it is very useful for generating scenario-based datasets. Five JOIN types down. Each one serves a unique purpose, and knowing when to use which one is what makes a great analyst. Which JOIN type surprised you the most? Let us talk in the comments! #DataAnalytics #SQL #LearningDataAnalytics #DataAnalyst #WithYouWithMe

In today's SQL lesson, we answer: "Is this user becoming more or less active?" You have monthly session data for every user. You want to know: Is Ana growing?  Is Ben churning? A regular query can't answer this, so you need context across rows. That's exactly what window functions are built for. Breaking it down: • OVER() is what makes it a window function.  Without it, SUM collapses rows like GROUP BY. With it, SUM computes a running total and every single row survives in the output. That's the core idea. • LAG(sessions) pulls the value from the previous row inside the window.  For February, it returns January's sessions. That's your month-over-month comparison in one column, no self-join needed. • PARTITION BY user_id resets the window for each user.  Without it, Ben's last row would bleed into Ana's first and your LAG values become noise. • ORDER BY month sets the row sequence inside each window.  Without order, "previous row" has no definition. For any ranking or time-based function, this is required. • LEAD() is the forward-looking twin of LAG.  It looks at the next row's value. Useful for predicting what a user does after a specific event. You can't get both the monthly breakdown and the running total from a GROUP BY. Window functions can give you both in the same query, on the same row. Where does this show up in real work? Every question about change over time is a window function waiting to happen. Is revenue growing month over month? → LAG on monthly totals Who are the top 3 customers per region? → RANK + PARTITION BY region What's the 7-day rolling average of signups? → AVG OVER with a frame clause Which users dropped off after their first week? → LEAD on session dates And that’s how an entire category of business questions becomes answerable in a single query. 🔖 Save this if you work with data. ✅ Follow me for more practical SQL, data engineering tips and automation breakdowns for teams that run on data.

Learning Data Analytics the Right Way Series - Ep. 41 SQL for Data Analysis | SQL JOINS Syntax 🟢 Last episode I talked about what a JOIN is and why it matters. Today we got into the actual syntax and I have to say, seeing it written out and understanding the logic behind it made everything click. Let me walk you through it. Here is the query I studied: SELECT ProductName, SUM(sales) AS TotalSales FROM sales s JOIN products p ON p.ProductID = s.ProductID GROUP BY ProductName ORDER BY TotalSales DESC Now let me break this down piece by piece. ✔️ SELECT ProductName, SUM(sales) AS TotalSales tells the database to retrieve the product name and calculate the total sales for each product. ✔️ The AS keyword simply renames the result column to TotalSales for easy reading. ✔️ FROM sales s sets the primary table as the sales table. The letter s is an alias, a shortcut name we assign to the table to keep the query clean and less repetitive. ✔️ JOIN products p brings in the products table and assigns it the alias p. This is where the two tables come together. ✔️ ON p.ProductID = s.ProductID is the join condition. It tells the database exactly how the two tables are related. Match the ProductID in the products table with the ProductID in the sales table. ✔️ GROUP BY ProductName groups the results by each product. ✔️ ORDER BY TotalSales DESC sorts everything from the highest total sales to the lowest. When executed, this query returns a ranked list of every product alongside its total sales, with the best performing product appearing at the top. One query. Two tables. Powerful results. Next episode we go deeper into the types of JOINS. Stay tuned! What part of this syntax stood out to you? Let us talk in the comments. #DataAnalytics #SQL #LearningDataAnalytics #DataAnalyst #WithYouWithMe

Learning Data Analytics the Right Way Series - Ep. 49 SQL for Data Analysis | Subqueries in the SELECT Clause 🟢 What if your query could figure out a value and use it right away? That's exactly what subqueries in the SELECT clause do. Today was one of those times when SQL seemed like real magic. A subquery in the SELECT clause is inside the SELECT statement. You can use it to do math or get values for each row in your result set on the fly. 🟢 Below is the query I built to find the top 3 products by sales percentage: SELECT p.ProductName, s. Sales, ROUND(s.Sales/(SELECT SUM(Sales) FROM sales),4)*100 AS sales_percentage FROM products p JOIN sales s ON s.ProductID=p.ProductID ORDER BY sales_percentage DESC LIMIT 3 🟢 The inner query sums up all the sales values in the sales table. The outer query then uses that value to calculate what percentage of total sales each product makes up. ROUND keeps the result neat. ORDER BY puts them in order from highest to lowest. LIMIT only pulls the top 3. A question. Calculations that change. Real business knowledge. 🟢 In the next episode, I will look at subqueries in the FROM clause. It keeps getting better! What business question would you ask this kind of question to get an answer? Leave a comment and share. #LearningDataAnalyticsTheRightWaySeries #DataAnalytics #SQL #LearningDataAnalytics #DataAnalyst #WithYouWithMe

📊 SQL for Data Analysis | Understanding JOINs Most real-world data doesn’t live in a single table. It’s spread across multiple sources — and to analyze it effectively, you need to know how to bring it together. That’s where SQL JOINs come in. 🔍 What are JOINs? JOINs allow you to combine rows from two or more tables using a common column (like customer_id or transaction_id). 🛠️ The “Big Four” you need to know: • INNER JOIN → Returns only matching records from both tables • LEFT JOIN → Returns all records from the left table + matching records from the right • RIGHT JOIN → Similar to LEFT JOIN, but keeps all records from the right table • FULL JOIN → Returns all records from both tables (matched + unmatched) 💡 Why this matters for analysts: JOINs are the foundation of real-world data analysis. Whether you are: • Reconciling data across systems • Matching transactions with user data • Identifying missing or unmatched records Understanding JOINs isn’t just about syntax — it’s about understanding relationships within your data. Which JOIN do you use the most in your queries? 👇 #SQL #DataAnalytics #SQLBasics #LearningJourney #FutureDataanalysis

🚀 Level Up Your SQL: Beyond the Basic SELECT If you want to move from just "pulling data" to building complex, high-performance reports, you need these three tools in your belt: Window Functions, CTEs, and Joins. 🛠️ Here is a quick breakdown of how they transform your data game: 🪟 Window Functions: The "Current Row" Specialist Unlike standard aggregates that group your data, Window Functions perform calculations across a set of rows while keeping your individual rows intact. Ranking: Use ROW_NUMBER(), RANK(), or DENSE_RANK() to organize your data. Running Totals: SUM() OVER() is the gold standard for tracking growth over time. Time Travel: Use LAG() and LEAD() to compare the current row to the one before or after it—perfect for period-over-period analysis. 🏗️ Common Table Expressions (CTE): Clean & Readable Tired of "spaghetti code" with too many subqueries? A CTE creates a temporary result set that you can reference like a table. The Syntax: Start with WITH CTE_Name AS (...) and then select from it. The Win: It makes your logic much easier to follow, debug, and maintain. 🔗 Joins: The Data Connector This is how we combine rows from different tables based on related columns. Inner Join: Only the matches. Left Join: Everything from the left table + matching right-side data. Full Outer: Everything from both sides, matches or not. Cross Join: A Cartesian product of both tables. 💡 Pro-Tips for the Road: ✅ Use Window Functions for rankings and running totals. ✅ Use CTEs to simplify complex logic your future self will thank you for the readability. ✅ Always add indexes to your join columns to keep your query performance snappy. SQL isn't just a language; it’s a way to tell a story with data. Mastering these essentials ensures your story is accurate, clean, and fast. Which SQL feature was the biggest "game changer" for your workflow? Let’s talk shop in the comments! 👇 #SQL #DataEngineering #BusinessIntelligence #DataAnalytics #CodingTips #Database #TechSkills #CareerGrowth #DataScience

(12-04-2026) From Data Entry to Data Analytics It was a complete deep dive into the "Analytical Power" of SQL. I’ve moved past just retrieving rows and started performing complex calculations and data transformations. 📈 The goal today was Manipulation & Aggregation. I wanted to learn how to take raw, messy data and turn it into a structured report. Here’s the toolkit I mastered today: 1. Organizing the Output (Ordering) ORDER BY: Learned how to sort my results in ASC (Ascending) or DESC (Descending). It’s simple, but essential for making data readable. 2. The Function Library (Transformation) I explored the built-in functions that allow me to modify data on the fly: String Functions: CONCAT, LOWER, UPPER, TRIM, SUBSTRING, REPLACE, LENGTH, and LEFT/RIGHT. 🔠 Numeric Functions: ABS, ROUND, CEIL, FLOOR, POW, SQRT, and MOD. 🔢 3. Data Summarization (Aggregates) This is where the real power lies. I mastered the "Big 5" Aggregate functions: COUNT(), SUM(), AVG(), MIN(), and MAX(). 4. The Analytics Duo: GROUP BY & HAVING This was the highlight of the day. GROUP BY: I can now categorize data to see the "big picture" (e.g., total sales per city or average grade per class). HAVING: I learned why we can't use WHERE with aggregate functions and mastered HAVING to filter my grouped data. It’s one thing to see 10,000 rows; it’s another thing to summarize them into 5 meaningful insights in a single query. #SQL #DataAnalytics #DataScience #MySQL #GroupBy #CodingLife #Day4 #RelationalDatabases

Day 12/365 — Mastering SQL by Understanding SQL JOINs — A Must-Know for Data Professionals SQL JOINs allow you to combine data from multiple tables and uncover meaningful insights. Here’s a simple breakdown: INNER JOIN Returns only the matching rows from both tables. Example: SELECT c.customer_name, o.order_id  FROM customers c  INNER JOIN orders o  ON c.customer_id = o.customer_id; LEFT JOIN (LEFT OUTER JOIN) Returns all rows from the left table + matching rows from the right. (If No match found - You’ll see NULLs.) Example: SELECT c.customer_name, o.order_id FROM customers c LEFT JOIN orders o ON c.customer_id = o.customer_id; Shows all customers, even those without orders. RIGHT JOIN (RIGHT OUTER JOIN) Returns all rows from the right table + matching rows from the left. Example: SELECT c.customer_name, o.order_id FROM customers c RIGHT JOIN orders o ON c.customer_id = o.customer_id; Shows all orders, even if customer details are missing. FULL JOIN (FULL OUTER JOIN) Returns all rows from both tables, whether there’s a match or not. Example: SELECT c.customer_name, o.order_id  FROM customers c  FULL JOIN orders o  ON c.customer_id = o.customer_id; CROSS JOIN Returns all possible combinations of rows between two tables. Example: SELECT p.product_name, c.category_name FROM products p CROSS JOIN categories c; Useful when generating combinations. SELF JOIN Joins a table with itself — useful for hierarchical data (like employee-manager relationships). Example: SELECT e.employee_name, m.employee_name AS manager FROM employees e JOIN employees m ON e.manager_id = m.employee_id; Useful for hierarchical relationships. Why this matters in the real world? Think about analyzing customer orders, tracking user activity, or building dashboards — JOINs help you bring scattered data together into one clear picture. #SQL #DataAnalytics #DataScience #Learning #TechCareers #SQLjoin 

Learning Data Analytics the Right Way Series - Ep. 44 SQL for Data Analysis | Constructing Queries with Many Elements 🟢 This is where everything begins to come together. Today I didn’t just learn a new concept; I actually built something using everything I’ve learned so far, and the feeling was wonderful. The task was to find the top 10 states in the US with the highest total discount received. 🟢 Here is the query I constructed: SELECT l.State, s.ProductID, SUM(Discount) AS TotalDiscount FROM sales s LEFT JOIN location l ON l.PostalCode = s.PostalCode GROUP BY l.State ORDER BY TotalDiscount DESC LIMIT 10 🟢 Let me walk you through the thinking behind the query above. I used a LEFT JOIN to connect the sales table to the location table through a shared PostalCode column. SUM calculated the total discount per state. GROUP BY organised the results by state. ORDER BY sorted them from highest to lowest. And LIMIT pulled out just the top 10. 🟢 And here are the results. Texas came out on top with a total discount of 364.64, followed by Pennsylvania at 192.90 and Illinois at 191.90. Ohio, California, and Florida rounded out the top six. North Carolina, Arizona, New York, and Colorado ranked among the top 10, with Colorado recording the lowest total discount of 57.60. One query pulling real insights from two connected tables. This is exactly what SQL is built for. Every clause learnt, every JOIN practised, and every function understood led to this moment. Consistency truly pays off. What query have you built recently that made you proud? Share in the comments! #DataAnalytics #SQL #LearningDataAnalytics #DataAnalyst #WithYouWithMe

🔤 SQL String Functions — Clean, Format & Standardize Text Data! Text fields often come messy: inconsistent casing, extra spaces, or missing formatting. SQL string functions help analysts tidy up text data so it’s consistent, searchable, and presentation‑ready. 🔹 1️⃣ CONCAT — Combine Text SELECT CONCAT(first_name, ' ', last_name) AS full_name FROM customers; 👉 Merge columns into a single readable field. 🔹 2️⃣ TRIM — Remove Extra Spaces SELECT TRIM(name) AS cleaned_name FROM customers; 👉 Eliminate unwanted spaces for consistency. 🔹 3️⃣ UPPER / LOWER — Standardize Case SELECT UPPER(city) AS city_upper, LOWER(email) AS email_lower FROM customers; 👉 Normalize text for easier comparisons and reporting. 🔹 4️⃣ SUBSTRING — Extract Parts of Text SELECT SUBSTRING(phone, 1, 3) AS area_code FROM customers; 👉 Pull out specific portions of text (like area codes). 💡 Analyst Tip: String functions are essential for data cleaning, reporting, and dashboard building. They ensure text fields are consistent and business‑friendly. 📢 Stay Tuned! Next in the SQL Tips Series: SQL Date Functions — learn how to analyze time‑based trends with YEAR(), MONTH(), DATEDIFF(), and more! #SQL #DataCleaning #DataAnalytics #DataAnalyst #SQLTips #LearningSQL #BusinessIntelligence #DataScience #CareerGrowth #Codebasics #DataDriven