Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 201 – Combining Query Results

Posted on December 9, 2005March 14, 2016 by slowder

Overview

There comes a point in your SQL career where you will need to combine the results of several queries into one data set, and present it in one view.  When you get to this point, you’ll need to be familiar with the UNION command.  With Microsoft SQL 2005, there are two new functions, similar to UNION that you should also be familiar with.  EXCEPT and INTERSECT allow you to do two common data operations, without building the logic yourself.  I’ll cover these three commands in this post.

I have a script that can build the tables I reference on this page here.

UNION

Consider the data in the following two queries.

SELECT productName
FROM products

SELECT productName
FROM productSale

productName
-------------
Mountain Dew
paper
pen
pencil

productName
--------------
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
paper
pencil
pencil

Most of the time you’ll get a request that basically asks you to combine these two outputs into one list.  The easiest way to do that is use UNION ALL.

SELECT
productName
FROM products
UNION ALL
SELECT productName
FROM productSale

Mountain Dew
paper
pen
pencil
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
Mountain Dew
paper
pencil
pencil

As soon as you combine these two outputs, you should notice there are duplicates.  Most of the time what you actually wanted to see here is a UNION.  UNION will actually remove the duplicates from the output for you.  This actually will return results much quicker than trying to apply DISTINCT to your results.

SELECT
   productName
FROM products
UNION
SELECT
   productName
FROM productSale

productName
-------------
Mountain Dew
paper
pen
pencil

There one important point to keep in mind while using UNION or UNION ALL. The number, order, and datatypes of the columns must be the same for every query you want to combine.  If you change any one of these, you will get an error from SQL informing you that this is true.

Combining queries’ results can be a useful feat when designing reports.  Definitely keep this trick in mind when you are faced with combining multiple data sets into one.

EXCEPT

The EXCEPT command actually builds on the concept of UNION.  If you have two result sets, and you need to see the results from the first set, where that record doesn’t exist in the second set, EXCEPT can be your friend.  EXCEPT can make it easier to do this than using a LEFT JOIN, and testing for no matches.

The same important point from UNION still applies.  You have to be dealing with two or more compatible record sets.

Let’s see what ProductNames exist in products, that doesn’t exist in productSale.

SELECT productName
FROM products
EXCEPT
SELECT productName
FROM productSale

productName
-------------
pen

INTERSECT

The INTERSECT command is the opposite of an EXCEPT.  It will only return the records that are in both record sets.

SELECT
   productName
FROM products
INTERSECT
SELECT
   productName
FROM productSale

productName
-------------
Mountain Dew
paper
pencil

Conclusion

Whenever you have to deal with multple record sets and need to combine them into one, keep these three commands in mind.  UNION is available in SQL 2000 and later, the EXCEPT and INTERSECT command is available in SQL 2005 and later.  All three can give you results that would take more work if you don’t use them.  I hope these examples have helped you understand them better, if not, let me know!

Previous: JOIN Next: INSERT

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme