Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 101 – Summarizing Data

Posted on October 20, 2005February 9, 2011 by slowder

This is the last of the lessons on functions for the 100 level.  I hope you’ve enjoyed them so far, but it’s time to wrap these up!

When beginning to learn SQL, it won’t be long until you have to answer questions that require you to summarize the data.  It’s one of the primary reasons SQL is used.  You store many records detailing events, then you can summarize that data and report it back to users, so they don’t have to summarize it by hand.

I’m going to show you the 5 most common ways you’ll be asked to summarize data: COUNT, SUM, MAX, MIN,and AVG (Average).  There are several more that SQL understands, and once you learn to define your own functions, there will be an
infinite number of ways to summarize that data.  I just want you to gain an understanding of the basics, so you can go on to all those other methods.

COUNT

There are three variations to this function

COUNT(*)
COUNT(ALL expression)
COUNT(DISTINCT expression)

The first method is the most common. You’ll use it when you want to count how many rows are in a table.  If we ran the following query against our products table we’ve referred to throughout the SQL 101 lessons, we get 4, since we only defined four records.

SELECT
   COUNT(*) AS [count]
FROM products
count
-----
4

We would get the same result from the following query.

SELECT
COUNT(ALL productName) AS [count]
FROM products

count
-----
4

If there were duplicates in the products table, and we only wanted a count of unique values, then the following version would let us count only the unique values in the table.

SELECT
COUNT(DISTINCT productName) AS [count]
FROM products

count
-----
4

Since there are no duplicates in our example table, we still get four.

SUM

Like COUNT, the sum function accepts ALL or DISTINCT as a modifier, but by default, it will sum all.  Sum is the first function that really interprets the data.  A COUNT is simple, a SUM actually does a little work for you.  Warning,
make sure the column your summing is a numeric type.  The sum function will try to convert the column into a numeric type, and if it finds even one value that cannot be converted, you will get an error.  You may also want to consider using the ISNULL function with this, since adding NULL to something is still NULL.

SELECT
SUM(price) AS [Total Price]
FROM products

Total Price
-----------
3.49

MAX, MIN, and AVG (average)

SQL is can be a great way to store lots of detail records. Whenever you have data, someone will eventually ask you to do some statistical analysis on that data. MAX, MIN, and average are the most common statistical numbers asked for.

SELECT
MAX(price) AS [max]
, MIN(price) AS [min]
, AVG(price) AS [average]
FROM products

max     min     average
----    ---     -------
1.25    .25     .8725

Conclusion

Summarizing data will be a big part of your life as a SQL developer.  These functions will serve as your first steps into learning more and more powerful ways to summarize data.

If you have any questions, please, feel free to send them in!  I’m here to help you learn as much as you can about SQL.

Previous: Calculated Fields Next: GROUP BY

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