\n
SELECT Employees.Employee_Name, Departments.Department_Name<\/p>\n
FROM Employees<\/p>\n
INNER JOIN Departments<\/p>\n
ON Employees.Department_ID = Departments.Department_ID;<\/p>\n<\/div><\/div>
In this example, SQL compares the Department_ID<\/strong> values from both tables and returns only the matching records.<\/p>INNER JOIN Output<\/strong><\/p>\n\n| Employee_Name<\/b><\/td>\n | Department_Name<\/b><\/td>\n<\/tr><\/thead>\n\n\n| Rahul<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table> Here, Rahul and Priya appear in the output because their Department_ID<\/strong> values exist in both tables. Arjun does not appear because Department_ID 3<\/strong> is not available in the Departments table. Similarly, Sneha is also excluded because her Department_ID is NULL<\/strong>.<\/p>INNER JOIN is widely used in real-world applications such as employee management systems, e-commerce platforms, banking systems, and reporting dashboards, where only matching records are required.<\/p> 2. SQL LEFT JOIN Explained<\/h3>LEFT JOIN returns all rows from the left table and the matching rows from the right table. If no matching value exists in the right table, SQL displays NULL<\/strong> values for those columns.<\/p>This join is useful when we want to keep all records from the main table even if related information is missing.<\/p> SQL LEFT JOIN Syntax<\/strong><\/p>\n SELECT Employees.Employee_Name, Departments.Department_Name<\/p>\n FROM Employees<\/p>\n LEFT JOIN Departments<\/p>\n ON Employees.Department_ID = Departments.Department_ID;<\/p>\n<\/div><\/div> LEFT JOIN Output<\/strong><\/p>\n\n| Employee_Name<\/b><\/td>\n | Department_Name<\/b><\/td>\n<\/tr><\/thead>\n\n\n| Rahul<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| Arjun<\/span><\/td>\n | NULL<\/span><\/td>\n<\/tr>\n\n| Sneha<\/span><\/td>\n | NULL<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table> In this result, all employees are displayed because the Employees table is placed on the left side of the query. Arjun receives NULL<\/strong> because Department_ID 3<\/strong> does not exist in the Departments table. Sneha also receives NULL<\/strong> because no department is assigned.<\/p>LEFT JOIN is commonly used in real-world scenarios such as:<\/p> \n- finding customers without orders,<\/li>\n
- students without course registrations,<\/li>\n
- employees without assigned projects,<\/li>\n
- or products without reviews.<\/li>\n<\/ul>
3. SQL RIGHT JOIN Explained<\/h3>RIGHT JOIN works opposite to LEFT JOIN. It returns all rows from the right table and only the matching rows from the left table. If no matching value exists in the left table, SQL fills the columns with NULL<\/strong>.<\/p>SQL RIGHT JOIN Syntax<\/strong><\/p>\n SELECT Employees.Employee_Name, Departments.Department_Name<\/p>\n FROM Employees<\/p>\n RIGHT JOIN Departments<\/p>\n ON Employees.Department_ID = Departments.Department_ID;<\/p>\n<\/div><\/div> RIGHT JOIN Output<\/strong><\/p>\n\n| Employee_Name<\/b><\/td>\n | Department_Name<\/b><\/td>\n<\/tr><\/thead>\n\n\n| Rahul<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| NULL<\/span><\/td>\n | Marketing<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table> In this example, the Marketing department appears even though no employee belongs to it because the Departments table is placed on the right side of the query.<\/p> In real projects, developers often prefer LEFT JOIN because it feels more natural to keep the primary table on the left side. However, RIGHT JOIN is still useful in situations where all records from the second table must be displayed.<\/p> 4. SQL FULL OUTER JOIN Explained<\/h3>FULL OUTER JOIN combines the results of both LEFT JOIN and RIGHT JOIN. It returns all matching rows along with unmatched rows from both tables. Whenever no match exists, SQL fills the missing columns with NULL<\/strong>.<\/p>This join is useful when we want complete visibility of records from both tables.<\/p> SQL FULL OUTER JOIN Syntax<\/strong><\/p>\n SELECT Employees.Employee_Name, Departments.Department_Name<\/p>\n FROM Employees<\/p>\n FULL OUTER JOIN Departments<\/p>\n ON Employees.Department_ID = Departments.Department_ID;<\/p>\n<\/div><\/div> FULL OUTER JOIN Output<\/strong><\/p>\n\n| Employee_Name<\/b><\/td>\n | Department_Name<\/b><\/td>\n<\/tr><\/thead>\n\n\n| Rahul<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| Arjun<\/span><\/td>\n | NULL<\/span><\/td>\n<\/tr>\n\n| Sneha<\/span><\/td>\n | NULL<\/span><\/td>\n<\/tr>\n\n| NULL<\/span><\/td>\n | Marketing<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table> In this output:<\/strong><\/p>\n- Rahul and Priya are matching records.<\/li>\n
- Arjun and Sneha appear because they exist only in the Employees table.<\/li>\n
- Marketing appears because it exists only in the Departments table.<\/li>\n<\/ul>
FULL OUTER JOIN is commonly used in reporting systems, analytics platforms, and auditing scenarios where both matched and unmatched data are important.<\/p> 5. SQL CROSS JOIN Explained<\/h3>CROSS JOIN combines every row from the first table with every row from the second table. Instead of checking matching conditions, SQL creates all possible combinations between the tables.<\/p> SQL CROSS JOIN Syntax<\/strong><\/p>\n SELECT Employees.Employee_Name, Departments.Department_Name<\/p>\n FROM Employees<\/p>\n CROSS JOIN Departments;<\/p>\n<\/div><\/div> CROSS JOIN Output<\/strong><\/p>\n\n| Employee_Name<\/b><\/td>\n | Department_Name<\/b><\/td>\n<\/tr><\/thead>\n\n\n| Rahul<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Rahul<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| Rahul<\/span><\/td>\n | Marketing<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| Priya<\/span><\/td>\n | Marketing<\/span><\/td>\n<\/tr>\n\n| Arjun<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Arjun<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n| Arjun<\/span><\/td>\n | Marketing<\/span><\/td>\n<\/tr>\n\n| Sneha<\/span><\/td>\n | HR<\/span><\/td>\n<\/tr>\n\n| Sneha<\/span><\/td>\n | Finance<\/span><\/td>\n<\/tr>\n\n | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
![\"fsd](\"https:\/\/www.placementpreparation.io\/blog\/wp-content\/uploads\/2025\/06\/fsd-image-web-horizontal.webp\")
<\/a><\/p>