CREATE INDEX syntax in SQL - Step-by-Step Execution

Concept Flow - CREATE INDEX syntax

Start CREATE INDEX

↓

Specify Index Name

↓

Specify Table Name

↓

Specify Column(s) to Index

↓

Execute Index Creation

↓

Index Created Successfully

↓

END

The CREATE INDEX command starts by naming the index, then specifying the table and columns to index, and finally creates the index to speed up queries.

Execution Sample

SQL

CREATE INDEX idx_name ON employees (last_name);

This command creates an index named idx_name on the last_name column of the employees table.

Execution Table

Step	Action	Details	Result
1	Start CREATE INDEX	Command recognized	Ready to create index
2	Specify Index Name	Index name = idx_name	Index name set
3	Specify Table	Table = employees	Table identified
4	Specify Column(s)	Column(s) = last_name	Columns identified for indexing
5	Execute Creation	Create index on employees(last_name)	Index idx_name created
6	End	Index creation complete	Ready for queries using index

💡 Index created successfully on employees.last_name column

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Index Name	None	idx_name	idx_name	idx_name	idx_name
Table Name	None	None	employees	employees	employees
Columns	None	None	None	last_name	last_name
Index Status	Not created	Not created	Not created	Not created	Created

Key Moments - 3 Insights

Why do we need to specify the index name explicitly?

The index name is required to identify the index later for maintenance or dropping. See execution_table step 2 where the index name is set before creation.

Can we create an index without specifying columns?

No, columns must be specified to tell the database which data to index. Step 4 in execution_table shows columns being identified before creation.

Does CREATE INDEX modify the table data?

No, it only creates a separate structure to speed up queries. The table data remains unchanged, as shown in step 5 where only the index is created.

Visual Quiz - 3 Questions

Look at the execution_table, what is the index name after step 2?

A last_name

B employees

C idx_name

D None

💡 Hint

Check the 'Index Name' variable in variable_tracker after step 2

At which step are the columns to be indexed specified?

A Step 4

B Step 3

C Step 1

D Step 5

💡 Hint

Look at the 'Specify Column(s)' action in execution_table

If we omit the index name, what would happen?

A The index is created with a default name

B The command will fail due to missing index name

C The table will be dropped

D The index will be created on all columns

💡 Hint

Index name is mandatory as shown in step 2 of execution_table

Concept Snapshot

CREATE INDEX syntax:
CREATE INDEX index_name ON table_name (column1, column2, ...);
- index_name: name you give to the index
- table_name: the table to add the index on
- columns: one or more columns to speed up searches
Creates a separate structure without changing table data
Improves query speed on indexed columns

Full Transcript

The CREATE INDEX command starts by naming the index, then specifying the table and columns to index. The database then creates the index structure to speed up queries on those columns. The index name is required to identify the index later. Columns must be specified to tell the database what to index. Creating an index does not change the table data. The process ends when the index is successfully created and ready for use.

Practice

1. What is the main purpose of using CREATE INDEX in a database?

easy

A. To speed up data retrieval by creating shortcuts on columns

B. To delete rows faster from a table

C. To backup the database automatically

D. To encrypt the data stored in the table

Solution

1. Step 1: Understand what an index does

   An index creates a shortcut to quickly find data in a column without scanning the whole table.

2. Step 2: Identify the main benefit

   This shortcut speeds up data retrieval, especially for searches and sorts.

3. Final Answer:

   To speed up data retrieval by creating shortcuts on columns -> Option A

4. Quick Check:

   CREATE INDEX improves search speed [OK]

Hint: Indexes speed up searches by creating shortcuts [OK]

Common Mistakes:

• Thinking indexes speed up data deletion
• Confusing indexes with backups
• Believing indexes encrypt data

2. Which of the following is the correct syntax to create an index named idx_name on the column last_name of the table employees?

easy

A. CREATE idx_name INDEX ON employees (last_name);

B. CREATE INDEX idx_name ON employees (last_name);

C. INDEX CREATE idx_name ON employees (last_name);

D. CREATE INDEX ON employees idx_name (last_name);

Solution

1. Step 1: Recall the standard CREATE INDEX syntax

   The correct syntax is: CREATE INDEX index_name ON table_name (column_name);

2. Step 2: Match the syntax with options

   CREATE INDEX idx_name ON employees (last_name); matches the correct order and keywords exactly.

3. Final Answer:

   CREATE INDEX idx_name ON employees (last_name); -> Option B

4. Quick Check:

   CREATE INDEX index_name ON table (column) [OK]

Hint: Remember: CREATE INDEX name ON table (column) [OK]

Common Mistakes:

• Swapping index name and table name positions
• Using wrong keyword order
• Omitting ON keyword

3. Given the table products(id INT, name VARCHAR, price DECIMAL), what will be the result of this SQL command?

CREATE INDEX idx_price ON products(price);

medium

A. The products table is duplicated with the name idx_price

B. The price column is deleted from the products table

C. An index named idx_price is created on the price column to speed up queries filtering by price

D. Syntax error because price is not a primary key

Solution

1. Step 1: Understand what the CREATE INDEX command does here

   The command creates an index named idx_price on the price column of products.

2. Step 2: Identify the effect of the index

   This index helps speed up queries that filter or sort by price without changing the table structure.

3. Final Answer:

   An index named idx_price is created on the price column to speed up queries filtering by price -> Option C

4. Quick Check:

   CREATE INDEX adds search speed, no deletion [OK]

Hint: CREATE INDEX speeds up search, does not delete or duplicate [OK]

Common Mistakes:

• Thinking index creation deletes columns
• Assuming index requires primary key
• Confusing index with table duplication

4. Identify the error in this SQL statement:

CREATE INDEX ON employees (last_name);

medium

A. Cannot create index on last_name column

B. Missing table name after ON

C. Incorrect use of parentheses around column name

D. Missing index name after CREATE INDEX

Solution

1. Step 1: Check the syntax of CREATE INDEX

   The syntax requires an index name after CREATE INDEX before ON.

2. Step 2: Identify the missing part

   The statement lacks the index name, which causes a syntax error.

3. Final Answer:

   Missing index name after CREATE INDEX -> Option D

4. Quick Check:

   CREATE INDEX must have a name [OK]

Hint: Always name your index after CREATE INDEX [OK]

Common Mistakes:

• Omitting the index name
• Confusing table name with index name
• Misplacing parentheses

5. You want to speed up queries that filter by both category and price columns in the items table. Which is the best way to create an index?

hard

A. CREATE INDEX idx_cat_price ON items (category, price);

B. CREATE INDEX idx_cat ON items (category); CREATE INDEX idx_price ON items (price);

C. CREATE INDEX idx_price_cat ON items (price, category);

D. CREATE INDEX idx_items ON items (category);

Solution

1. Step 1: Understand multi-column index usage

   A single index on (category, price) helps queries filtering by both columns efficiently.

2. Step 2: Compare options

   CREATE INDEX idx_cat_price ON items (category, price); creates a composite index on category and price in that order, which is best for combined filters.

3. Final Answer:

   CREATE INDEX idx_cat_price ON items (category, price); -> Option A

4. Quick Check:

   Composite index on both columns is best [OK]

Hint: Use composite index for multiple columns searched together [OK]

Common Mistakes:

• Creating separate indexes instead of composite
• Wrong column order in composite index
• Creating index on only one column when filtering by two