AUTO_INCREMENT vs SERIAL vs IDENTITY in SQL - Hands-On Comparison

Understanding AUTO_INCREMENT, SERIAL, and IDENTITY in SQL

📖 Scenario: You are creating a simple database table to store user information for a website. Each user needs a unique ID that automatically increases as new users are added.

🎯 Goal: Build three versions of a user table using AUTO_INCREMENT, SERIAL, and IDENTITY to understand how each method creates an auto-incrementing primary key.

📋 What You'll Learn

Create a table named users_auto_increment using AUTO_INCREMENT for the ID column.

Create a table named users_serial using SERIAL for the ID column.

Create a table named users_identity using IDENTITY for the ID column.

💡 Why This Matters

🌍 Real World

Auto-incrementing IDs are used in real databases to uniquely identify records without manual input, making data management easier and more reliable.

💼 Career

Understanding these auto-increment methods is essential for database developers and administrators to design efficient and consistent database schemas.

1

Create a table with AUTO_INCREMENT

Write a SQL statement to create a table called users_auto_increment with two columns: id as an integer primary key that uses AUTO_INCREMENT, and username as a variable character string of length 50.

SQL

-- Your SQL code here to create users_auto_increment table with AUTO_INCREMENT

Hint

Use AUTO_INCREMENT after the id column type to make it auto-increment in MySQL.

2

Create a table with SERIAL

Write a SQL statement to create a table called users_serial with two columns: id as a SERIAL primary key, and username as a variable character string of length 50.

SQL

-- Your SQL code here to create users_serial table with SERIAL

Hint

Use SERIAL as the type for the id column in PostgreSQL to auto-increment.

3

Create a table with IDENTITY

Write a SQL statement to create a table called users_identity with two columns: id as an integer primary key using IDENTITY(1,1), and username as a variable character string of length 50.

SQL

-- Your SQL code here to create users_identity table with IDENTITY

Hint

Use IDENTITY(1,1) for the id column in SQL Server to auto-increment.

4

Add a sample insert for each table

Write three SQL insert statements to add a user with username 'alice' into each table: users_auto_increment, users_serial, and users_identity. Do not specify the id value; let it auto-increment.

SQL

-- Your SQL code here to insert 'alice' into each table without specifying id

Hint

Insert only the username column; the id will auto-increment automatically.

Practice

1. Which keyword is used in MySQL to automatically generate unique numbers for a primary key column?

easy

A. IDENTITY

B. SERIAL

C. SEQUENCE

D. AUTO_INCREMENT

Solution

1. Step 1: Understand MySQL auto-numbering

   MySQL uses AUTO_INCREMENT to generate unique numbers automatically for columns like primary keys.

2. Step 2: Compare with other keywords

   SERIAL is PostgreSQL-specific, IDENTITY is SQL standard used in SQL Server and newer PostgreSQL versions, and SEQUENCE is a separate object, not a column keyword.

3. Final Answer:

   AUTO_INCREMENT -> Option D

4. Quick Check:

   MySQL auto-number = AUTO_INCREMENT [OK]

Hint: MySQL uses AUTO_INCREMENT for auto numbering [OK]

Common Mistakes:

• Confusing SERIAL with MySQL syntax
• Using IDENTITY in MySQL
• Thinking SEQUENCE is a column keyword

2. Which of the following is the correct syntax to create an auto-incrementing primary key column in PostgreSQL using the SERIAL keyword?

easy

A. CREATE TABLE users (id SERIAL PRIMARY KEY, name VARCHAR(50));

B. CREATE TABLE users (id AUTO_INCREMENT PRIMARY KEY, name VARCHAR(50));

C. CREATE TABLE users (id IDENTITY PRIMARY KEY, name VARCHAR(50));

D. CREATE TABLE users (id SEQUENCE PRIMARY KEY, name VARCHAR(50));

Solution

1. Step 1: Identify PostgreSQL SERIAL syntax

   In PostgreSQL, SERIAL is used as a shorthand to create an integer column that auto-increments.

2. Step 2: Check syntax correctness

   CREATE TABLE users (id SERIAL PRIMARY KEY, name VARCHAR(50)); uses id SERIAL PRIMARY KEY, which is valid. Options B and C use MySQL and SQL Server syntax incorrectly in PostgreSQL. CREATE TABLE users (id SEQUENCE PRIMARY KEY, name VARCHAR(50)); uses SEQUENCE incorrectly as a column type.

3. Final Answer:

   CREATE TABLE users (id SERIAL PRIMARY KEY, name VARCHAR(50)); -> Option A

4. Quick Check:

   SERIAL syntax in PostgreSQL = CREATE TABLE users (id SERIAL PRIMARY KEY, name VARCHAR(50)); [OK]

Hint: PostgreSQL uses SERIAL for auto-increment columns [OK]

Common Mistakes:

• Using AUTO_INCREMENT in PostgreSQL
• Using IDENTITY without parentheses
• Treating SEQUENCE as a column type

3. Given the following SQL Server table creation statement, what will be the output of inserting two rows without specifying the ID column?

CREATE TABLE products (id INT IDENTITY(1,1) PRIMARY KEY, name VARCHAR(20));
INSERT INTO products (name) VALUES ('Pen');
INSERT INTO products (name) VALUES ('Pencil');
SELECT * FROM products;

medium

A. [{"id": null, "name": "Pen"}, {"id": null, "name": "Pencil"}]

B. [{"id": 0, "name": "Pen"}, {"id": 1, "name": "Pencil"}]

C. [{"id": 1, "name": "Pen"}, {"id": 2, "name": "Pencil"}]

D. Syntax error on INSERT statements

Solution

1. Step 1: Understand IDENTITY behavior in SQL Server

   The IDENTITY(1,1) means the ID column starts at 1 and increments by 1 automatically for each new row.

2. Step 2: Predict inserted values

   Inserting two rows without specifying ID will assign IDs 1 and 2 respectively. The SELECT will show these IDs with names.

3. Final Answer:

   [{"id": 1, "name": "Pen"}, {"id": 2, "name": "Pencil"}] -> Option C

4. Quick Check:

   IDENTITY auto increments IDs starting at 1 [OK]

Hint: IDENTITY(1,1) starts numbering from 1 incrementing by 1 [OK]

Common Mistakes:

• Assuming ID starts at 0
• Expecting null IDs without insert values
• Thinking INSERT needs ID value explicitly

4. You try to create a table in PostgreSQL with this statement:

CREATE TABLE orders (order_id INT AUTO_INCREMENT PRIMARY KEY, order_date DATE);

What is the error and how to fix it?

medium

A. AUTO_INCREMENT is invalid in PostgreSQL; use SERIAL or IDENTITY instead

B. Missing parentheses after AUTO_INCREMENT

C. order_id must be VARCHAR for AUTO_INCREMENT

D. No error; statement is correct

Solution

1. Step 1: Identify AUTO_INCREMENT support

   PostgreSQL does not support AUTO_INCREMENT; this is a MySQL keyword.

2. Step 2: Correct PostgreSQL syntax

   Use SERIAL or GENERATED AS IDENTITY for auto-incrementing columns in PostgreSQL.

3. Final Answer:

   AUTO_INCREMENT is invalid in PostgreSQL; use SERIAL or IDENTITY instead -> Option A

4. Quick Check:

   PostgreSQL uses SERIAL or IDENTITY, not AUTO_INCREMENT [OK]

Hint: PostgreSQL rejects AUTO_INCREMENT; use SERIAL or IDENTITY [OK]

Common Mistakes:

• Trying to use MySQL syntax in PostgreSQL
• Assuming AUTO_INCREMENT works everywhere
• Ignoring error messages about syntax

5. You want to migrate a MySQL table with AUTO_INCREMENT primary key to PostgreSQL. Which approach correctly preserves auto-increment behavior?

hard

A. Keep AUTO_INCREMENT keyword as is in PostgreSQL

B. Replace AUTO_INCREMENT with SERIAL type for the primary key column

C. Use IDENTITY without specifying start value

D. Manually insert IDs for each row without auto-increment

Solution

1. Step 1: Understand MySQL to PostgreSQL migration

   MySQL uses AUTO_INCREMENT, but PostgreSQL does not support it directly.

2. Step 2: Use PostgreSQL equivalent

   PostgreSQL uses SERIAL as a shorthand for auto-increment integer columns, preserving behavior.

3. Final Answer:

   Replace AUTO_INCREMENT with SERIAL type for the primary key column -> Option B

4. Quick Check:

   MySQL AUTO_INCREMENT -> PostgreSQL SERIAL [OK]

Hint: Use SERIAL in PostgreSQL to replace MySQL AUTO_INCREMENT [OK]

Common Mistakes:

• Leaving AUTO_INCREMENT keyword unchanged
• Using IDENTITY without proper syntax
• Manually managing IDs instead of auto-increment