DDL (CREATE, ALTER, DROP) in DBMS Theory - Time & Space Complexity

Time Complexity: DDL (CREATE, ALTER, DROP)

O(m)

Understanding Time Complexity

When working with database structure commands like CREATE, ALTER, and DROP, it's important to understand how the time to complete these commands changes as the database grows.

We want to know how the execution time changes when the database has more tables or larger table definitions.

Scenario Under Consideration

Analyze the time complexity of the following DDL commands.

-- Create a new table
CREATE TABLE Employees (
  ID INT PRIMARY KEY,
  Name VARCHAR(100),
  Department VARCHAR(50)
);

-- Alter the table to add a new column
ALTER TABLE Employees ADD Salary DECIMAL(10,2);

-- Drop the table
DROP TABLE Employees;
    

These commands create a table, modify its structure, and then remove it from the database.

Identify Repeating Operations

Look for operations that repeat or scale with input size.

• Primary operation: Scanning metadata and updating system catalogs for the table.
• How many times: Usually once per command, but may involve checking existing table definitions or dependencies.

How Execution Grows With Input

Execution time depends mostly on the size of the table definition and related metadata, not on the number of rows.

Input Size (n)	Approx. Operations
Small table (few columns)	Few operations, quick execution
Medium table (dozens of columns)	More operations, slightly longer
Large table (hundreds of columns)	More metadata to process, longer time

Pattern observation: Time grows roughly with the size of the table structure, not the data inside.

Final Time Complexity

Time Complexity: O(m)

This means the time to execute DDL commands grows linearly with the size of the table's structure (number of columns or constraints).

Common Mistake

[X] Wrong: "DDL commands take longer as the number of rows in the table grows."

[OK] Correct: DDL commands mainly change the table structure, not the data, so the number of rows usually does not affect execution time.

Interview Connect

Understanding how DDL commands scale helps you explain database management tasks clearly and shows you grasp how databases handle structure changes efficiently.

Self-Check

"What if we altered a table with many foreign key constraints? How would the time complexity change?"

Practice

1. What does the CREATE statement do in a database?

easy

A. It makes a new table to store data.

B. It deletes an existing table and its data.

C. It changes the data inside a table.

D. It backs up the database.

Solution

1. Step 1: Understand the purpose of CREATE

   The CREATE statement is used to make new database objects, such as tables, to store data.

2. Step 2: Compare with other statements

   DROP deletes tables, ALTER changes structure, but CREATE makes new tables.

3. Final Answer:

   It makes a new table to store data. -> Option A

4. Quick Check:

   CREATE = Make new table [OK]

Hint: CREATE always makes new tables, not deletes or changes [OK]

Common Mistakes:

• Confusing CREATE with DROP which deletes tables
• Thinking CREATE changes existing data
• Assuming CREATE backs up data

2. Which of the following is the correct syntax to add a new column named age of type INT to an existing table students?

easy

A. ALTER students ADD age INT;

B. ALTER TABLE students ADD COLUMN age INT;

C. DROP TABLE students ADD age INT;

D. CREATE TABLE students ADD age INT;

Solution

1. Step 1: Identify correct ALTER syntax

   The correct syntax to add a column is: ALTER TABLE table_name ADD COLUMN column_name datatype;

2. Step 2: Check each option

   ALTER TABLE students ADD COLUMN age INT; matches the correct syntax. Options B and C misuse CREATE and DROP. ALTER students ADD age INT; misses TABLE keyword.

3. Final Answer:

   ALTER TABLE students ADD COLUMN age INT; -> Option B

4. Quick Check:

   ALTER TABLE + ADD COLUMN = ALTER TABLE students ADD COLUMN age INT; [OK]

Hint: ALTER TABLE ... ADD COLUMN ... is the correct form [OK]

Common Mistakes:

• Omitting TABLE keyword after ALTER
• Using CREATE or DROP instead of ALTER
• Forgetting the COLUMN keyword (optional but clearer)

3. Consider the following SQL commands executed in order:
CREATE TABLE employees (id INT, name VARCHAR(50));
ALTER TABLE employees ADD COLUMN salary INT;
What will be the structure of the employees table after these commands?

medium

A. Table with columns: id, name, salary

B. Table with columns: id, salary

C. Table with columns: id, name

D. Table with columns: name, salary

Solution

1. Step 1: Analyze CREATE TABLE command

   The first command creates a table named employees with columns id and name.

2. Step 2: Analyze ALTER TABLE command

   The second command adds a new column salary to the employees table.

3. Final Answer:

   Table with columns: id, name, salary -> Option A

4. Quick Check:

   CREATE + ALTER ADD COLUMN = id, name, salary [OK]

Hint: ALTER ADD COLUMN adds new columns to existing tables [OK]

Common Mistakes:

• Ignoring the ALTER command effect
• Assuming DROP was used to remove columns
• Thinking ALTER replaces columns instead of adding

4. Identify the error in the following SQL statement:
ALTER TABLE employees DROP salary;

medium

A. Table name is incorrect

B. DROP cannot be used with ALTER TABLE

C. Missing COLUMN keyword after DROP

D. salary column does not exist

Solution

1. Step 1: Understand DROP syntax in ALTER TABLE

   To remove a column, syntax requires: ALTER TABLE table_name DROP COLUMN column_name;

2. Step 2: Check the given statement

   The statement misses the COLUMN keyword after DROP, causing syntax error.

3. Final Answer:

   Missing COLUMN keyword after DROP -> Option C

4. Quick Check:

   ALTER TABLE DROP COLUMN required [OK]

Hint: DROP COLUMN must be used, not just DROP [OK]

Common Mistakes:

• Omitting COLUMN keyword after DROP
• Confusing DROP TABLE with DROP COLUMN
• Assuming DROP alone removes columns

5. You want to permanently delete a table named orders and all its data from the database. Which SQL command should you use?

hard

A. ALTER TABLE orders DELETE;

B. ALTER TABLE orders DROP;

C. CREATE TABLE orders;

D. DROP TABLE orders;

Solution

1. Step 1: Understand the purpose of DROP TABLE

   DROP TABLE deletes the entire table and its data permanently from the database.

2. Step 2: Evaluate the options

   DROP TABLE orders; uses correct syntax. ALTER TABLE orders DROP; and D misuse ALTER. CREATE TABLE orders; creates a table instead of deleting.

3. Final Answer:

   DROP TABLE orders; -> Option D

4. Quick Check:

   DROP TABLE = delete table permanently [OK]

Hint: Use DROP TABLE to delete tables permanently [OK]

Common Mistakes:

• Using ALTER instead of DROP to delete tables
• Confusing CREATE with DROP
• Omitting TABLE keyword in DROP statement