Why DDL (CREATE, ALTER, DROP) in DBMS Theory? - Purpose & Use Cases

The Big Idea

What if you could rebuild your entire data system with just a few simple commands?

The Scenario

Imagine you have a huge notebook where you keep all your important records. Now, you want to add a new section, change the title of an existing section, or remove a section you no longer need. Doing this by hand means flipping through pages, rewriting titles, and carefully erasing sections without messing up the rest.

The Problem

Manually managing your records is slow and risky. You might accidentally erase important information, lose track of changes, or spend hours just organizing. It's hard to keep everything consistent and up to date without making mistakes.

The Solution

DDL commands like CREATE, ALTER, and DROP let you tell the database exactly how to build, change, or remove parts of your data structure quickly and safely. Instead of rewriting everything by hand, you give clear instructions that the system follows perfectly every time.

Before vs After

✗ Before

Write new pages, cross out old titles, erase sections carefully

✓ After

CREATE TABLE students (...);
ALTER TABLE students ADD COLUMN age INT;
DROP TABLE old_records;

What It Enables

With DDL, you can easily design and modify your database structure, making data management efficient and error-free.

Real Life Example

A school database needs to add a new column for student email addresses. Instead of rewriting the entire student list, the admin uses ALTER to add the column instantly.

Key Takeaways

DDL commands control the structure of databases.

CREATE builds new tables or objects.

ALTER changes existing structures without losing data.

DROP removes unwanted tables or objects safely.

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