Sequences and auto-increment in Snowflake - Commands & Configuration

Introduction

When you want to create unique numbers automatically for each new row in a table, sequences help by generating these numbers one after another without repeats.

When you need a unique ID for each new record in a table without manually entering it.

When multiple users insert data at the same time and you want to avoid duplicate IDs.

When you want to control the starting number and increment step of IDs.

When you want to reuse a sequence number in different tables consistently.

When you want to generate numbers outside of table inserts for other purposes.

Commands

This command creates a new sequence named 'my_sequence' that starts at 1 and increases by 1 each time it is used.

Terminal

CREATE SEQUENCE my_sequence START = 1 INCREMENT = 1;

Expected Output

Sequence MY_SEQUENCE successfully created.

This command gets the next number from the sequence, which will be 1 the first time it runs.

Terminal

SELECT my_sequence.NEXTVAL;

Expected Output

NEXTVAL

1

This creates a table 'users' where the 'id' column automatically gets the next sequence number when a new row is added.

Terminal

CREATE TABLE users (id NUMBER DEFAULT my_sequence.NEXTVAL, name STRING);

Expected Output

Table USERS successfully created.

This inserts two new users. Their 'id' values will be automatically assigned from the sequence.

Terminal

INSERT INTO users (name) VALUES ('Alice'), ('Bob');

Expected Output

2 rows inserted.

This shows all rows in the 'users' table with their auto-incremented IDs.

Terminal

SELECT * FROM users;

Expected Output

ID | NAME

1  | Alice

2  | Bob

Key Concept

If you remember nothing else from this pattern, remember: sequences generate unique numbers automatically and safely for new data entries.

Common Mistakes

Not using NEXTVAL to get the next sequence number and trying to insert sequence name directly.

The sequence name alone does not produce a number; NEXTVAL must be called to get the next value.

Always use sequence_name.NEXTVAL to get the next number from the sequence.

Creating a sequence but not linking it as a default value in the table column.

Without linking, the sequence won't auto-assign IDs during inserts.

Set the column default to sequence_name.NEXTVAL when creating or altering the table.

Assuming sequence numbers reset automatically after reaching a max value.

Sequences keep increasing unless explicitly altered or dropped.

Manage sequence limits manually if needed, or recreate the sequence to reset.

Summary

Create a sequence to generate unique numbers starting from a chosen value.

Use sequence_name.NEXTVAL to get the next number from the sequence.

Set a table column default to the sequence's NEXTVAL for automatic numbering on inserts.

Insert rows without specifying the ID; the sequence assigns it automatically.

Query the table to see the auto-incremented IDs assigned.

Practice

1. What is the main purpose of a sequence in Snowflake?

easy

A. To create backup copies of tables

B. To store large text data efficiently

C. To automatically generate unique numeric values

D. To manage user permissions

Solution

1. Step 1: Understand what a sequence does

   A sequence generates numbers automatically, usually for unique IDs.

2. Step 2: Identify the correct purpose

   Among the options, only automatic unique number generation matches the sequence's role.

3. Final Answer:

   To automatically generate unique numeric values -> Option C

4. Quick Check:

   Sequence = unique number generator [OK]

Hint: Sequences generate unique numbers automatically [OK]

Common Mistakes:

• Confusing sequences with tables
• Thinking sequences store text data
• Assuming sequences manage permissions

2. Which of the following is the correct syntax to get the next value from a sequence named order_seq?

easy

A. SELECT order_seq.NEXTVAL();

B. SELECT NEXTVAL('order_seq');

C. SELECT NEXTVAL(order_seq);

D. SELECT order_seq.nextval;

Solution

1. Step 1: Recall Snowflake sequence syntax

   Snowflake uses sequence_name.NEXTVAL() dot notation to get the next value.

2. Step 2: Match syntax to options

   Only SELECT order_seq.NEXTVAL(); uses the correct syntax.

3. Final Answer:

   SELECT order_seq.NEXTVAL(); -> Option A

4. Quick Check:

   Use seq_name.NEXTVAL() syntax [OK]

Hint: Use seq_name.NEXTVAL() [OK]

Common Mistakes:

• Omitting quotes around sequence name
• Passing non-string to NEXTVAL()
• Missing parentheses on NEXTVAL call

3. Given the sequence user_seq starting at 1000 and incrementing by 5, what will be the output of these two queries executed in order?

SELECT NEXTVAL('user_seq');
SELECT NEXTVAL('user_seq');

medium

A. 1005 and 1010

B. 1000 and 1001

C. 1000 and 1005

D. 1 and 2

Solution

1. Step 1: Understand sequence start and increment

   The sequence starts at 1000 and adds 5 each time NEXTVAL is called.

2. Step 2: Calculate the two NEXTVAL calls

   First call returns 1005, second call returns 1010.

3. Final Answer:

   1005 and 1010 -> Option A

4. Quick Check:

   Start=1000, increment=5, next two values = 1005, 1010 [OK]

Hint: First value = start + increment, next adds increment again [OK]

Common Mistakes:

• Assuming first NEXTVAL returns start value
• Confusing start value with first increment
• Thinking sequence resets after one call

4. You created a sequence with:
CREATE SEQUENCE invoice_seq START = 1 INCREMENT = 1;
But when you run SELECT NEXTVAL('invoice_seq'); you get an error. What is the most likely cause?

medium

A. Sequence name must be uppercase

B. Sequence was not committed or created properly

C. NEXTVAL function does not exist in Snowflake

D. You must specify schema name in NEXTVAL

Solution

1. Step 1: Check sequence creation and commit

   Sequences must be created successfully and committed before use.

2. Step 2: Identify common error cause

   If NEXTVAL errors, often the sequence does not exist or creation failed.

3. Final Answer:

   Sequence was not committed or created properly -> Option B

4. Quick Check:

   Sequence must exist before NEXTVAL call [OK]

Hint: Ensure sequence creation succeeded before NEXTVAL [OK]

Common Mistakes:

• Assuming case sensitivity causes error
• Thinking NEXTVAL is unsupported
• Forgetting to commit or check creation

5. You want to create a table orders with an auto-incrementing order_id using a sequence order_seq. Which approach correctly assigns order_id during insert?

hard

A. Create sequence and use INSERT INTO orders VALUES (order_seq + 1, ...);

B. Create sequence and use INSERT INTO orders VALUES (NEXTVAL('order_seq'), ...);

C. Create sequence and manually increment order_id in application code

D. Create sequence and set order_id default to order_seq.NEXTVAL()

Solution

1. Step 1: Understand how to use sequences in inserts

   Sequences provide unique numbers via NEXTVAL function during insert statements.

2. Step 2: Evaluate options for assigning order_id

   Only B correctly sets the order_id column default to order_seq.NEXTVAL() for automatic assignment on insert (when column omitted).

3. Final Answer:

   Create sequence and set order_id default to order_seq.NEXTVAL() -> Option D

4. Quick Check:

   Column DEFAULT seq.NEXTVAL() [OK]

Hint: Set column DEFAULT seq_name.NEXTVAL() [OK]

Common Mistakes:

• Trying to use sequence name directly without NEXTVAL
• Manually incrementing IDs in app code
• Using invalid syntax like order_seq + 1