I can teach you analytics!  I have never seen a database do analytics better than Snowflake.  This week we are working on the RANK command.

All of these examples have come from my books and training classes. Please do me a favor and tell your training coordinator that you know the best technical trainer in the World. Ask them to hire me to train at your company, either on-site or with a virtual class. They can see our classes, outlines, and a sample of my teaching at this link on our website. I hope to meet you and say thanks in my next class at your company:)

https://coffingdw.com/education/

In each example, you will see an ORDER BY statement, but it will not come at the end of the query.  The ORDER BY keywords is always within the RANK calculation.  It is the ORDER BY statement that determines what we are ranking.

In its most simple explanation, a RANK will sort the data first via the ORDER BY statement, and then give the first row rank of 1.  It will rank the second row with a two unless the value of row one and row two are equal.  Check out the example below.

Nexus Query Chameleon from Coffing Data Warehousing queries, migrates, and federates across all database systems.

In the picture above, notice that an open and close parenthesis immediately follows the keyword RANK.  The open and close parenthesis insinuates a function.  There is never anything inside the parenthesis, but it is required.  The keyword OVER follows, which represents that this analytic is an ordered analytic, which is interchangeable with the term window function. The term ordered analytic means that the data set will be put in a specific order before the calculation begins.  We sort the data using the ORDER BY statement, and in this example, we are sorting by the Daily_Sales column.  Since the default for an ORDER BY statement is ascending, we are ranking the data by Daily_Sales ASC.

When you first see a RANK command with nothing in the parenthesis, you might have trouble at first and think, “What are we ranking?”  Just check out the column in the ORDER BY statement, and that is what you are ranking.  We have an ORDER BY Daily_Sales, so we are ranking by Daily_Sales.

The first two rows both have a value of 32,800.50, so they both get a rank of 1.  Rows one and two are tied, but notice that row three gets a rank of 3.  There are no more ties after that so each row gets the next sequential ranking.

Quite often, a user will want to give the highest value the number one rank.  Check out the example below because we are going to use the ORDER BY to rank the Daily_Sales column in DESC order.

The phrase below sounds like a protest chant:

What are we ranking? Daily_Sales!

How are we ranking it? Descending order!

Each RANK example will have an ORDER BY statement, but sometimes you will also have a PARTITION statement.  In the example below, you see the keywords PARTITION BY, and that means the RANK function will reset and start over.  Our ORDER BY statement is ordering the data by the column Daily_Sales DESC, so Daily_Sales is what we are ranking, but we will reset the rank calculation and start over with each Product_ID break because the column Product_ID is in the PARTITION BY statement.  Check out the next example below.

Nexus Chameleon in Dark Mode

Now, get ready for something you have never seen before, which is the QUALIFY statement.  QUALIFY acts like a filter, but it is different than a WHERE clause filter.  The QUALIFY statement waits until all of the analytic calculations finish.  When the report finishes and is ready to return, the QUALIFY steps in and filters the rows further.

In the example below, we are attempting to find the top three Daily_Sales per Product_ID.  It is the QUALIFY statement that dictates the top three Daily_Sales.

Let’s review.  We rank by Daily_Sales DESC because of the ORDER BY Daily_Sales DESC statement.  We reset the calculation on each Product_ID break because of the PARTITION BY Product_ID statement.  And finally, after the entire ranking occurs, we further filter to get only the top three Daily_Sales per Product_ID because of the Qualify statement.  Notice we have given our RANK analytic an alias name for the report in which we call RANK1.  So, we QUALIFY RANK1 < 4, which means give me the first three rows.

Nexus Chameleon using Book Ends Mode to place the answer set to the right of the query window.

The only systems I have ever seen that use the QUALIFY statements are Snowflake, Teradata, BigQuery, and Databricks.  If you are working with a system that does not support QUALIFY, you can place your SQL statement in a derived table, and then use a WHERE clause.

In the example below, all of the SQL using the color blue and red is part of the derived table.  The results are the same as the previous example, but it is done with a derived table and not a QUALIFY statement.

You are about to see something not often seen, and that is the DENSE_RANK.  It works exactly like the RANK command, but RANK and DENSE_RANK handle ties differently.  In our example below, we are using both the RANK and DENSE_RANK functions.  Since both of them have the same ORDER BY Daily_Sales statement, the data comes out the same with the only difference being how they handle the ties.  The first two rows get a rank of one since they both tie with a value of 32,800.50.   The RANK gives the third row a ranking of three, and the DENSE_RANK gives it the third-row a ranking of two.

The example below shows the PERCENT_RANK function.  Percent_Rank finds out the relative rank of a row in a group. The formula to get Percent_Rank is

(RANK-1 / (Total Rows -1).

Did you know that Coffing Data Warehousing is the first company to create software that joins data across all systems? Download your free Nexus trial at www.CoffingDW.com.

Watch how the Nexus performs federated queries to Join a Snowflake table to tables from twenty systems. Watch the video.

Posted in Blog and tagged