Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 301 — WITH CUBE and ROLLUP

Posted on January 11, 2010February 9, 2011 by slowder

Have you been asked to summarize some data into a nice report for management? They want to see subtotals and grand totals you say?

You don’t have to drop the results of your GROUP BY statement into a temp table, and summarize the subtotals yourself. The SQL ROLLUP and CUBE commands offer a valuable tool for gaining some quick and easy insight into your data.

WITH ROLLUP you’ll get a subtotal for each combination of grouped columns, from right to left. So you can get multiple outputs of a ROLLUP statement, based on the order you enter your columns into your select and GROUP BY statements. Make sure you enter them in least restrictive to most restrictive.

Think hierarchy, and you’ll be ok!

WITH CUBE is more complex. It will give you summary for each combination of the columns you enter. I’ll show you an example later to make this a bit more clear.

Let’s return to our KOTOR database. It’s a database I use to store data about items in the game Knights of the Old Republic. In that database suppose the following data exists:

Items for sale:

Type Store Number
Blaster Tatooine 12
Shield Tatooine 18
Lightsaber Crystal Dantooine 4
Blaster Dantooine 14
Shield Korriban 9
Blaster Korriban 5
Lightsaber Crystal Korriban 1

As the proud owners of these shops, we’d like to take a quick look at various aspects of our inventory. Let’s take a look at the data using WITH CUBE:

SELECT Type, Store, SUM(Number) as Number
FROM items
GROUP BY type,store
WITH CUBE

And the results of the query:

Type Store Number
Shield Tatooine 18
Shield Korriban 9
Shield NULL 27
Blaster Tatooine 12
Blaster Korriban 5
Blaster Dantooine 14
Blaster NULL 31
Lightsaber Crystal Korriban 1
Lightsaber Crystal Dantooine 4
Lightsaber Crystal NULL 5
NULL NULL 63
NULL Tatooine 30
NULL Korriban 15
NULL Dantooine 18

Wow! That’s a lot of data! Notice that we are presented with a number of additional groupings that contain NULL fields that wouldn’t appear in the results of a normal GROUP BY command. These are the summarization rows added by the CUBE statement. Analyzing the data, you’ll notice that our chain has 27 Shields, 31 Blasters and 5 Lightsaber Crystals spread among our three stores. Our Tatooine store has the largest number of items in stock with a whopping inventory of 30 items.

We’re not particularly interested in the total number of items at each store — we’d just like to know our galaxy-wide inventory of each item along with the standard GROUP BY data. Utilizing the ROLLUP operator instead of the CUBE operator will eliminate the results that contain a NULL in the first column.

Here’s the SQL:

SELECT Type, Store, SUM(Number) as Number
FROM items
GROUP BY type,store
WITH ROLLUP

And the results:

Type Store Number
Shield Tatooine 18
Shield Korriban 9
Shield NULL 27
Blaster Tatooine 12
Blaster Korriban 5
Blaster Dantooine 14
Blaster NULL 31
Lightsaber Crystal Korriban 1
Lightsaber Crystal Dantooine 4
Lightsaber Crystal NULL 5
NULL NULL 63

And that’s CUBE and ROLLUP in a nutshell! There’s plenty more to go, I need to show you the GROUPING function and the GROUPING SETS feature. I’ll get to those as soon as I can. If you have any questions, please let me know!

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