UNION ALL with duplicates in SQL

Introduction

Use UNION ALL to combine results from two or more queries and keep all rows, including duplicates.

You want to combine customer lists from two different stores and keep all entries, even if some customers appear in both.

You need to merge sales data from two months and want to see every sale, including repeated ones.

You want to combine two lists of products from different suppliers and keep all products, even if some are the same.

You want to add new records to an existing list without removing duplicates.

Syntax

SQL

SELECT column1, column2 FROM table1
UNION ALL
SELECT column1, column2 FROM table2;

UNION ALL keeps all rows from both queries, including duplicates.

Columns selected in both queries must match in number and type.

Examples

Combines names from employees and contractors, showing all names even if repeated.

SQL

SELECT name FROM employees
UNION ALL
SELECT name FROM contractors;

Lists all products and prices from two stores, including duplicates.

SQL

SELECT product_id, price FROM store1
UNION ALL
SELECT product_id, price FROM store2;

Sample Program

This example creates two tables with fruit names. The query combines all fruits from both tables, including duplicates like 'Apple' and 'Banana'.

SQL

CREATE TABLE fruits1 (name VARCHAR(20));
CREATE TABLE fruits2 (name VARCHAR(20));

INSERT INTO fruits1 VALUES ('Apple'), ('Banana'), ('Cherry');
INSERT INTO fruits2 VALUES ('Banana'), ('Date'), ('Apple');

SELECT name FROM fruits1
UNION ALL
SELECT name FROM fruits2;

Important Notes

UNION ALL is faster than UNION because it does not check for duplicates.

Use UNION if you want to remove duplicates instead.

Summary

UNION ALL combines results from multiple queries and keeps duplicates.

Both queries must select the same number of columns with compatible types.

Use UNION ALL when you want to keep all rows without filtering duplicates.

Practice

1. What does the SQL statement UNION ALL do when combining results from two queries?

easy

A. It combines rows but removes duplicates.

B. It combines all rows from both queries including duplicates.

C. It only returns rows that appear in both queries.

D. It returns rows only from the first query.

Solution

1. Step 1: Understand UNION ALL behavior

   UNION ALL combines results from two queries and keeps all rows, including duplicates.

2. Step 2: Compare with UNION

   Unlike UNION, UNION ALL does not remove duplicate rows.

3. Final Answer:

   It combines all rows from both queries including duplicates. -> Option B

4. Quick Check:

   UNION ALL keeps duplicates = A [OK]

Hint: UNION ALL keeps duplicates, UNION removes them [OK]

Common Mistakes:

• Confusing UNION ALL with UNION
• Thinking duplicates are removed
• Assuming it returns only unique rows

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

easy

A. SELECT col1 FROM table1 UNIONALL SELECT col1 FROM table2;

B. SELECT col1 FROM table1 UNION ALL FROM table2;

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

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

Solution

1. Step 1: Check correct UNION ALL syntax

   The correct syntax is to write two SELECT statements separated by 'UNION ALL'.

2. Step 2: Identify syntax errors in options

   SELECT col1 FROM table1 UNIONALL SELECT col1 FROM table2; writes UNIONALL as one word (missing space), SELECT col1 FROM table1 UNION ALL FROM table2; misses the second SELECT keyword, SELECT col1 FROM table1 UNION ALL SELECT FROM table2; misses columns after the second SELECT. SELECT col1 FROM table1 UNION ALL SELECT col1 FROM table2; uses correct syntax.

3. Final Answer:

   SELECT col1 FROM table1 UNION ALL SELECT col1 FROM table2; -> Option C

4. Quick Check:

   Correct UNION ALL syntax = B [OK]

Hint: UNION ALL needs space and two SELECTs [OK]

Common Mistakes:

• Writing UNIONALL as one word
• Missing SELECT in second query
• Incorrect keyword order

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 ALL SELECT id FROM B;

medium

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

B. [1, 2, 3, 4]

C. [1, 2, 3]

D. [2, 3, 4]

Solution

1. Step 1: List rows from first query

   SELECT id FROM A returns [1, 2, 3].

2. Step 2: List rows from second query

   SELECT id FROM B returns [2, 3, 4].

3. Step 3: Combine results with UNION ALL

   UNION ALL keeps duplicates, so combined list is [1, 2, 3, 2, 3, 4].

4. Final Answer:

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

5. Quick Check:

   UNION ALL keeps duplicates = A [OK]

Hint: UNION ALL stacks all rows, duplicates included [OK]

Common Mistakes:

• Removing duplicates like UNION
• Listing only unique values
• Ignoring order of combined rows

4. Consider this SQL query:
SELECT name FROM employees UNION ALL SELECT name FROM departments;
It returns an error. What is the most likely cause?

medium

A. The two SELECT statements have different numbers of columns.

B. UNION ALL cannot be used with SELECT statements.

C. The keyword ALL is not allowed after UNION.

D. The tables employees and departments must have the same name.

Solution

1. Step 1: Check column counts in both SELECTs

   UNION ALL requires both SELECTs to have the same number of columns.

2. Step 2: Identify error cause

   If employees and departments tables have different columns selected, error occurs.

3. Final Answer:

   The two SELECT statements have different numbers of columns. -> Option A

4. Quick Check:

   Column count mismatch causes error = C [OK]

Hint: Both SELECTs must have same columns count [OK]

Common Mistakes:

• Thinking UNION ALL disallows duplicates only
• Assuming table names must match
• Believing ALL keyword is invalid

5. You have two tables:
Sales_2023: product_id, quantity_sold
Sales_2024: product_id, quantity_sold
You want to create a combined list of all sales including duplicates for analysis. Which query correctly uses UNION ALL and also adds a column year to identify the source year?

hard

A. SELECT product_id, quantity_sold, 'year' FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, 'year' FROM Sales_2024;

B. SELECT product_id, quantity_sold FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, '2024' AS year FROM Sales_2024;

C. SELECT product_id, quantity_sold, year FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, year FROM Sales_2024;

D. SELECT product_id, quantity_sold, '2023' AS year FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, '2024' AS year FROM Sales_2024;

Solution

1. Step 1: Add year column with literal values

   Use '2023' and '2024' as string literals to add a year column in each SELECT.

2. Step 2: Ensure both SELECTs have same columns

   Both SELECTs must have product_id, quantity_sold, and year columns for UNION ALL.

3. Step 3: Combine with UNION ALL

   SELECT product_id, quantity_sold, '2023' AS year FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, '2024' AS year FROM Sales_2024; correctly combines both tables with year column and keeps duplicates.

4. Final Answer:

   SELECT product_id, quantity_sold, '2023' AS year FROM Sales_2023 UNION ALL SELECT product_id, quantity_sold, '2024' AS year FROM Sales_2024; -> Option D

5. Quick Check:

   Matching columns with year literals + UNION ALL = D [OK]

Hint: Add year as literal in both SELECTs for UNION ALL [OK]

Common Mistakes:

• Mismatched columns count in SELECTs
• Using column name 'year' without value
• Forgetting to alias literals as year