Why Finding gaps in sequences in SQL? - Purpose & Use Cases

The Big Idea

What if you could find missing numbers in seconds instead of hours of tedious checking?

The Scenario

Imagine you have a list of invoice numbers, but some numbers are missing. You try to find which invoice numbers are skipped by scanning the list one by one on paper or in a spreadsheet.

The Problem

Checking each number manually is slow and tiring. It's easy to miss gaps or make mistakes, especially if the list is long. You waste time and might deliver wrong reports.

The Solution

Using SQL to find gaps in sequences lets you quickly spot missing numbers with a simple query. The database does the hard work, so you get accurate results fast without manual errors.

Before vs After

✗ Before

Look at each number in the list and write down missing ones by hand.

✓ After

SELECT number + 1 AS missing_start FROM invoices WHERE number + 1 NOT IN (SELECT number FROM invoices);

What It Enables

This lets you instantly find missing entries in any ordered list, making data checks and audits easy and reliable.

Real Life Example

A company uses this to find missing invoice numbers to ensure all sales are recorded and no transactions are lost.

Key Takeaways

Manually finding gaps is slow and error-prone.

SQL queries can quickly identify missing sequence numbers.

This improves accuracy and saves time in data management.

Practice

1. What is the main purpose of using the LEAD() function when finding gaps in a sequence of numbers in SQL?

easy

A. To find the maximum number in the sequence

B. To compare each number with the next number in the sequence

C. To sum all numbers in the sequence

D. To sort the numbers in descending order

Solution

1. Step 1: Understand the role of LEAD()

   The LEAD() function allows you to look at the next row's value in the current row's context.

2. Step 2: Identify how LEAD() helps find gaps

   By comparing the current number with the next number, you can detect if there is a gap (difference greater than 1).

3. Final Answer:

   To compare each number with the next number in the sequence -> Option B

4. Quick Check:

   LEAD() compares current and next values [OK]

Hint: Use LEAD() to peek at the next number in sequence [OK]

Common Mistakes:

• Thinking LEAD() sums values
• Confusing LEAD() with aggregate functions
• Using LEAD() to sort data

2. Which of the following SQL snippets correctly uses LEAD() to find gaps in a sequence column named num in table numbers?

easy

A. SELECT num, LEAD(num) AS next_num FROM numbers;

B. SELECT num, LEAD(num) FROM numbers ORDER BY num;

C. SELECT num, LEAD(num) OVER (ORDER BY num) AS next_num FROM numbers;

D. SELECT num, LEAD(num) OVER () AS next_num FROM numbers;

Solution

1. Step 1: Check LEAD() syntax

   The correct syntax requires LEAD(column) OVER (ORDER BY column) to define the order for the window function.

2. Step 2: Identify the correct option

   SELECT num, LEAD(num) OVER (ORDER BY num) AS next_num FROM numbers; uses LEAD(num) OVER (ORDER BY num), which is the correct form to get the next number in order.

3. Final Answer:

   SELECT num, LEAD(num) OVER (ORDER BY num) AS next_num FROM numbers; -> Option C

4. Quick Check:

   LEAD() needs OVER with ORDER BY [OK]

Hint: Always include OVER(ORDER BY column) with LEAD() [OK]

Common Mistakes:

• Omitting OVER clause
• Not specifying ORDER BY inside OVER
• Using LEAD() without alias

3. Given the table numbers with column num containing values (1, 2, 4, 5, 7), what will the following query return?

SELECT num, LEAD(num) OVER (ORDER BY num) AS next_num FROM numbers;

medium

A. [{num:1, next_num:2}, {num:2, next_num:4}, {num:4, next_num:5}, {num:5, next_num:7}, {num:7, next_num:null}]

B. [{num:1, next_num:1}, {num:2, next_num:2}, {num:4, next_num:4}, {num:5, next_num:5}, {num:7, next_num:7}]

C. [{num:1, next_num:3}, {num:2, next_num:4}, {num:4, next_num:6}, {num:5, next_num:7}, {num:7, next_num:null}]

D. [{num:1, next_num:null}, {num:2, next_num:null}, {num:4, next_num:null}, {num:5, next_num:null}, {num:7, next_num:null}]

Solution

1. Step 1: Understand LEAD() output

   LEAD(num) returns the next row's num value ordered by num. So each row shows its own num and the next number.

2. Step 2: Apply to given data

   For values 1,2,4,5,7:
   1's next is 2
   2's next is 4
   4's next is 5
   5's next is 7
   7 has no next, so null

3. Final Answer:

   [{num:1, next_num:2}, {num:2, next_num:4}, {num:4, next_num:5}, {num:5, next_num:7}, {num:7, next_num:null}] -> Option A

4. Quick Check:

   LEAD() shifts values down by one [OK]

Hint: LEAD() shows next row's value or null if none [OK]

Common Mistakes:

• Assuming LEAD() repeats current value
• Expecting gaps filled automatically
• Confusing LEAD() with LAG()

4. The following query is intended to find gaps in the num sequence but returns no rows:

SELECT num FROM numbers WHERE LEAD(num) OVER (ORDER BY num) - num > 1;

What is the error?

medium

A. You cannot use window functions directly in WHERE clause

B. The ORDER BY inside LEAD() is missing

C. The subtraction operator is invalid here

D. LEAD() requires a GROUP BY clause

Solution

1. Step 1: Understand window function restrictions

   Window functions like LEAD() cannot be used directly in the WHERE clause because WHERE filters rows before window functions are applied.

2. Step 2: Correct approach

   Use a subquery or CTE to compute LEAD() first, then filter in an outer query.

3. Final Answer:

   You cannot use window functions directly in WHERE clause -> Option A

4. Quick Check:

   Window functions not allowed in WHERE [OK]

Hint: Use subquery or CTE to filter on window function results [OK]

Common Mistakes:

• Trying to filter window function in WHERE
• Missing OVER clause
• Expecting LEAD() to work like aggregate

5. You have a table orders with an integer column order_id that should be sequential but may have missing numbers. Which query correctly finds all missing order_id values between the minimum and maximum present?

hard

A. SELECT order_id FROM orders WHERE LEAD(order_id) - order_id > 1;

B. SELECT DISTINCT order_id + 1 FROM orders WHERE order_id + 1 NOT IN (SELECT order_id FROM orders);

C. SELECT order_id FROM orders WHERE order_id NOT IN (SELECT order_id FROM orders);

D. WITH seq AS (SELECT generate_series(MIN(order_id), MAX(order_id)) AS id FROM orders) SELECT id FROM seq LEFT JOIN orders ON seq.id = orders.order_id WHERE orders.order_id IS NULL;

Solution

1. Step 1: Generate full sequence range

   Use generate_series from minimum to maximum order_id to create all possible IDs.

2. Step 2: Find missing IDs by left join

   Left join this sequence to existing orders and select IDs where no matching order exists (NULL in orders).

3. Final Answer:

   WITH seq AS (SELECT generate_series(MIN(order_id), MAX(order_id)) AS id FROM orders) SELECT id FROM seq LEFT JOIN orders ON seq.id = orders.order_id WHERE orders.order_id IS NULL; -> Option D

4. Quick Check:

   Generate full range, then find missing with LEFT JOIN [OK]

Hint: Generate full range then find missing with LEFT JOIN [OK]

Common Mistakes:

• Using LEAD() alone misses multiple gaps
• Incorrect NOT IN subquery logic
• Assuming order_id + 1 always missing