Why UNION combining result sets in SQL? - Purpose & Use Cases

The Big Idea

What if you could combine multiple lists into one with a single simple command?

The Scenario

Imagine you have two separate lists of customer orders from two different stores saved in separate files. You want to see all orders together in one list to understand total sales.

The Problem

Manually copying and pasting orders from one list to another is slow and mistakes happen easily. You might miss some orders or duplicate others, making your final list unreliable.

The Solution

The UNION command in SQL lets you combine these two lists into one clean, unified list automatically. It saves time and ensures no duplicates sneak in unless you want them.

Before vs After

✗ Before

Copy orders from Store1 list
Paste into Master list
Copy orders from Store2 list
Paste into Master list

✓ After

SELECT * FROM Store1Orders
UNION
SELECT * FROM Store2Orders

What It Enables

With UNION, you can easily merge multiple sets of data into one complete view for better decisions.

Real Life Example

A business owner combines sales data from multiple branches to see total revenue without errors or extra work.

Key Takeaways

Manually merging data is slow and error-prone.

UNION combines multiple result sets into one automatically.

This makes data analysis faster and more reliable.

Practice

1. What does the SQL UNION operator do when combining results from two SELECT queries?

easy

A. Combines rows but keeps all duplicates

B. Combines rows from both queries and removes duplicate rows

C. Joins tables based on a common column

D. Filters rows based on a condition

Solution

1. Step 1: Understand UNION behavior

   The UNION operator combines rows from two or more SELECT queries into a single result set.

2. Step 2: Check duplicate handling

   By default, UNION removes duplicate rows to ensure unique results.

3. Final Answer:

   Combines rows from both queries and removes duplicate rows -> Option B

4. Quick Check:

   UNION removes duplicates = A [OK]

Hint: UNION removes duplicates by default, unlike UNION ALL [OK]

Common Mistakes:

• Confusing UNION with UNION ALL
• Thinking UNION joins tables by columns
• Assuming UNION filters rows

2. Which of the following is the correct syntax to combine two SELECT queries using UNION?

easy

A. SELECT col1 FROM table1 UNION ALL JOIN SELECT col1 FROM table2;

B. SELECT col1 FROM table1 JOIN SELECT col1 FROM table2;

C. SELECT col1 FROM table1 WHERE UNION SELECT col1 FROM table2;

D. SELECT col1 FROM table1 UNION SELECT col1 FROM table2;

Solution

1. Step 1: Review correct UNION syntax

   The correct syntax is to write two SELECT statements separated by the UNION keyword.

2. Step 2: Identify invalid options

   Options B, C, and D misuse JOIN or WHERE with UNION, which is incorrect syntax.

3. Final Answer:

   SELECT col1 FROM table1 UNION SELECT col1 FROM table2; -> Option D

4. Quick Check:

   UNION syntax = SELECT ... UNION SELECT ... [OK]

Hint: UNION joins SELECTs directly, no JOIN or WHERE needed [OK]

Common Mistakes:

• Using JOIN instead of UNION
• Placing WHERE before UNION
• Combining UNION ALL with JOIN incorrectly

3. Given two tables:
Table A: id
1
2
3
Table B: id
2
3
4
What is the result of:
SELECT id FROM A UNION SELECT id FROM B;

medium

A. [1, 2, 3, 4]

B. [1, 2, 2, 3, 3, 4]

C. [2, 3]

D. [1, 4]

Solution

1. Step 1: List rows from both tables

   Table A has ids 1, 2, 3; Table B has ids 2, 3, 4.

2. Step 2: Apply UNION behavior

   UNION combines all rows and removes duplicates, so final list is 1, 2, 3, 4.

3. Final Answer:

   [1, 2, 3, 4] -> Option A

4. Quick Check:

   UNION removes duplicates = [1, 2, 3, 4] [OK]

Hint: UNION removes duplicates, so no repeated ids appear [OK]

Common Mistakes:

• Expecting duplicates to appear
• Confusing UNION with UNION ALL
• Listing only common ids

4. Consider this SQL query:
SELECT name FROM employees UNION SELECT name, department FROM managers;
What is the issue with this query?

medium

A. The number of columns in both SELECT statements differ

B. UNION cannot be used with SELECT statements

C. The query will return duplicate rows

D. The query is missing a WHERE clause

Solution

1. Step 1: Check column counts in SELECTs

   The first SELECT returns 1 column (name), the second returns 2 columns (name, department).

2. Step 2: Understand UNION column rules

   UNION requires all SELECT statements to have the same number of columns with compatible types.

3. Final Answer:

   The number of columns in both SELECT statements differ -> Option A

4. Quick Check:

   UNION needs same columns = C [OK]

Hint: UNION needs same column count in all SELECTs [OK]

Common Mistakes:

• Ignoring column count mismatch
• Thinking UNION filters duplicates only
• Assuming WHERE clause is mandatory

5. You have two tables:
Sales2023(product, amount)
Apple, 100
Banana, 150
Sales2024(product, amount)
Banana, 200
Cherry, 300
Write a query using UNION to list all unique products sold in both years, sorted alphabetically.

hard

A. SELECT product, amount FROM Sales2023 UNION SELECT product, amount FROM Sales2024 ORDER BY amount;

B. SELECT product FROM Sales2023 UNION ALL SELECT product FROM Sales2024 ORDER BY product;

C. SELECT product FROM Sales2023 UNION SELECT product FROM Sales2024 ORDER BY product;

D. SELECT product FROM Sales2023 JOIN Sales2024 ON product ORDER BY product;

Solution

1. Step 1: Select product column from both tables

   We want unique products, so select only the product column from both tables.

2. Step 2: Use UNION to combine and remove duplicates

   UNION combines both lists and removes duplicates, giving unique products.

3. Step 3: Sort results alphabetically

   ORDER BY product sorts the final list alphabetically.

4. Final Answer:

   SELECT product FROM Sales2023 UNION SELECT product FROM Sales2024 ORDER BY product; -> Option C

5. Quick Check:

   UNION + ORDER BY product = B [OK]

Hint: Use UNION to remove duplicates, ORDER BY to sort [OK]

Common Mistakes:

• Using UNION ALL which keeps duplicates
• Selecting amount column when only product needed
• Using JOIN instead of UNION