Why PRIMARY KEY constraint in SQL? - Purpose & Use Cases

The Big Idea

What if your important data got mixed up or lost because there was no way to tell records apart?

The Scenario

Imagine you have a big notebook where you write down your friends' phone numbers. But you don't have any order or special mark to find a specific friend quickly. Sometimes you accidentally write the same friend's number twice, or you forget which number belongs to whom.

The Problem

Without a clear way to identify each friend uniquely, searching for a number becomes slow and confusing. Mistakes happen easily, like duplicate entries or missing information, making the notebook unreliable and frustrating to use.

The Solution

The PRIMARY KEY constraint acts like a special label on each friend's entry that must be unique and never empty. It helps the database quickly find, update, or delete the exact record without confusion or mistakes.

Before vs After

✗ Before

INSERT INTO friends (name, phone) VALUES ('Alice', '12345');
INSERT INTO friends (name, phone) VALUES ('Alice', '12345'); -- duplicate allowed

✓ After

CREATE TABLE friends (
  id INT PRIMARY KEY,
  name VARCHAR(50),
  phone VARCHAR(20)
);
INSERT INTO friends (id, name, phone) VALUES (1, 'Alice', '12345');
INSERT INTO friends (id, name, phone) VALUES (1, 'Alice', '12345'); -- error: duplicate id

What It Enables

It makes sure every record is unique and easy to find, enabling fast and reliable data management.

Real Life Example

In a school database, each student has a unique student ID as a PRIMARY KEY. This prevents confusion between students with the same name and helps teachers quickly access each student's records.

Key Takeaways

PRIMARY KEY ensures each record is unique and not empty.

It prevents duplicate or missing important data.

It helps databases find and manage data quickly and accurately.

Practice

1. What is the main purpose of a PRIMARY KEY in a database table?

easy

A. To speed up database backups

B. To uniquely identify each row and prevent null values

C. To store large text data

D. To allow duplicate values in a column

Solution

1. Step 1: Understand the role of PRIMARY KEY

   A PRIMARY KEY uniquely identifies each row and does not allow nulls, ensuring data integrity.

2. Step 2: Compare options with PRIMARY KEY purpose

   Options A, B, and C do not describe uniqueness or null restriction, which are key features of PRIMARY KEY.

3. Final Answer:

   To uniquely identify each row and prevent null values -> Option B

4. Quick Check:

   PRIMARY KEY = unique + not null [OK]

Hint: PRIMARY KEY means unique and no nulls [OK]

Common Mistakes:

• Thinking PRIMARY KEY allows duplicates
• Confusing PRIMARY KEY with foreign key
• Assuming PRIMARY KEY stores large text

2. Which of the following is the correct syntax to define a PRIMARY KEY on the id column during table creation?

easy

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

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

C. CREATE TABLE users (id INT, PRIMARY KEY name);

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

Solution

1. Step 1: Review correct PRIMARY KEY syntax inline

   PRIMARY KEY is declared after the column type, like id INT PRIMARY KEY.

2. Step 2: Check each option's syntax

   CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(50)); correctly places PRIMARY KEY after id INT. Options B, C, and D have syntax errors or misplaced keywords.

3. Final Answer:

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

4. Quick Check:

   PRIMARY KEY follows column type inline [OK]

Hint: PRIMARY KEY goes right after column type [OK]

Common Mistakes:

• Placing PRIMARY KEY after wrong column
• Using PRIMARY KEY without parentheses for multiple columns
• Syntax errors with misplaced keywords

3. Given the table creation:

CREATE TABLE orders (
  order_id INT,
  product_id INT,
  PRIMARY KEY (order_id, product_id)
);

What will happen if you try to insert two rows with the same order_id but different product_id?

medium

A. Only the second row will be inserted

B. Only the first row will be inserted; second causes error

C. Both rows cause a syntax error

D. Both rows will be inserted successfully

Solution

1. Step 1: Understand composite PRIMARY KEY behavior

   The PRIMARY KEY is on both order_id and product_id together, so uniqueness is checked on the pair.

2. Step 2: Analyze insertion of rows with same order_id but different product_id

   Since product_id differs, the pair is unique, so both rows can be inserted without error.

3. Final Answer:

   Both rows will be inserted successfully -> Option D

4. Quick Check:

   Composite PRIMARY KEY = unique pairs [OK]

Hint: Composite key means unique pairs, not single columns [OK]

Common Mistakes:

• Assuming order_id alone must be unique
• Thinking composite key allows duplicates in all columns
• Confusing syntax error with constraint violation

4. Consider this table creation:

CREATE TABLE employees (
  emp_id INT,
  email VARCHAR(100),
  PRIMARY KEY emp_id
);

What is wrong with this statement?

medium

A. PRIMARY KEY must be declared with parentheses around column name

B. PRIMARY KEY cannot be on emp_id column

C. email column must be PRIMARY KEY instead

D. Table cannot have a PRIMARY KEY

Solution

1. Step 1: Check syntax for table-level PRIMARY KEY

   When declaring PRIMARY KEY separately, column names must be inside parentheses, like PRIMARY KEY (emp_id).

2. Step 2: Identify error in given statement

   The statement misses parentheses around emp_id, causing syntax error.

3. Final Answer:

   PRIMARY KEY must be declared with parentheses around column name -> Option A

4. Quick Check:

   Table-level PRIMARY KEY needs parentheses [OK]

Hint: Table-level PRIMARY KEY needs parentheses [OK]

Common Mistakes:

• Omitting parentheses in table-level PRIMARY KEY
• Thinking PRIMARY KEY can't be on emp_id
• Confusing column-level and table-level syntax

5. You want to create a table students where each student is uniquely identified by a combination of student_id and campus_id. Which of the following statements correctly enforces this using a PRIMARY KEY?

hard

A. CREATE TABLE students (student_id INT PRIMARY KEY, campus_id INT PRIMARY KEY);

B. CREATE TABLE students (student_id INT, campus_id INT, PRIMARY KEY student_id, campus_id);

C. CREATE TABLE students (student_id INT, campus_id INT, PRIMARY KEY (student_id, campus_id));

D. CREATE TABLE students (student_id INT, campus_id INT, UNIQUE (student_id, campus_id));

Solution

1. Step 1: Understand composite PRIMARY KEY requirement

   To uniquely identify rows by two columns, a composite PRIMARY KEY on both columns is needed.

2. Step 2: Evaluate each option's correctness

   CREATE TABLE students (student_id INT, campus_id INT, PRIMARY KEY (student_id, campus_id)); correctly defines a composite PRIMARY KEY. CREATE TABLE students (student_id INT PRIMARY KEY, campus_id INT PRIMARY KEY); tries to assign two PRIMARY KEYs, which is invalid. CREATE TABLE students (student_id INT, campus_id INT, PRIMARY KEY student_id, campus_id); has syntax errors. CREATE TABLE students (student_id INT, campus_id INT, UNIQUE (student_id, campus_id)); uses UNIQUE but not PRIMARY KEY.

3. Final Answer:

   CREATE TABLE students (student_id INT, campus_id INT, PRIMARY KEY (student_id, campus_id)); -> Option C

4. Quick Check:

   Composite PRIMARY KEY uses parentheses around columns [OK]

Hint: Use parentheses for composite PRIMARY KEY columns [OK]

Common Mistakes:

• Trying multiple PRIMARY KEYs on separate columns
• Missing parentheses in PRIMARY KEY declaration
• Using UNIQUE instead of PRIMARY KEY for uniqueness