SQL UNION vs UNION ALL
Append result sets with or without duplicate removal.
What this solves
Combine two plant extracts into one report. This pattern is useful when the business question is clear but a generic tutorial is too abstract.
The rule
UNION removes duplicates; UNION ALL keeps every row and is usually cheaper.
SELECT Material FROM PlantA
UNION ALL
SELECT Material FROM PlantB;Real-work checklist
- Define the business key and expected grain before writing the formula, query or markup.
- Test the pattern on a small known sample where you can verify the answer manually.
- Check missing values, duplicates and data types before trusting a large result.
- Scale to the real file or database only after the logic is proven.
Common mistake
Do not use UNION just to hide accidental duplicates upstream.