HardSQL challenge #198WINDOW FUNCTIONPARTITIONRANKING

Rank Products by Price Within Each Category

Add a rank to every product, ordered by price and restarting for each category.

The challenge runs on the SQLabHub practice database (SQLite) and uses the products table. You can solve it in the browser, with nothing to install.

Solve This SQL Challenge

The task

Rank products by price within each category.

A correct answer returns 120 rows with 11 columns: id, name, category, price, cost, stock, sku, status, rating, review_count, rnk.

Tables used in this challenge

products 120 rows

id INTEGER (PK) · name TEXT · category TEXT · price REAL · cost REAL · stock INTEGER · sku TEXT · status TEXT · rating REAL · review_count INTEGER

First 3 rows of the products table
idnamecategorypricecoststockskustatusratingreview_count
1Play Kitchen DeluxeToys1786.38589.51257SKU-000001active457
2Micro-Cut Paper Shredder 8-SheetOffice Supplies907.93281.46131SKU-000002active2.5447
34K Dual Dash CameraAutomotive568.89204.8176SKU-000003active4.129

The first rows of each table are shown. See how all the tables relate on the database schema page.

Expected output

Expected output of the challenge
idnamecategorypricecoststockskustatusratingreview_countrnk
612000A Jump Starter PackAutomotive1948.86915.96338SKU-000061active4.3431
22Back Seat OrganizerAutomotive1804.31685.64428SKU-000022active31312
60Leather Steering Wheel CoverAutomotive1727.7915.6810SKU-000060active2.64003
10Magnetic Phone Mount ProAutomotive1599.08495.71411SKU-000010active3.11764
77Leather Steering Wheel CoverAutomotive1527.59641.59105SKU-000077active32585

First 5 of 120 rows. This is the output of the model solution on the practice database. The task does not fix a sort order, so your rows may come back in a different order.

What you practise

  • Ranking rows with RANK() or DENSE_RANK() and handling ties
  • Restarting a window calculation for each group with PARTITION BY

Hint and approach

Try the challenge first. Open these only when you need them.

Show the hint

PARTITION BY category

Show the step-by-step approach

How the model solution is built, in the order the database evaluates it:

  1. Read from the products table.
  2. Rank the rows with RANK(), ordered by price descending, restarting for each category. Tied rows share a rank and the next rank is skipped.

Model solution

Checking your session…

What to watch for

PARTITION BY restarts the numbering for each category while keeping every row; GROUP BY would collapse them. With RANK(), two products at the same price share a rank and the next rank is skipped.

  • RANK() and DENSE_RANK(). RANK() skips numbers after a tie (1, 1, 3) and DENSE_RANK() does not (1, 1, 2). Filtering on rank <= N returns more than N rows when there are ties.
  • PARTITION BY. PARTITION BY is not GROUP BY: it keeps every row and only decides which rows a window function looks at.
Solve This SQL Challenge

Same technique, other tables

More practice on this pattern with different columns:

Keep learning