CREATE TABLE syntax in SQL - Time & Space Complexity

Time Complexity: CREATE TABLE syntax

O(n)

Understanding Time Complexity

We want to understand how the time it takes to create a table changes as the table definition grows.

Specifically, how does adding more columns or constraints affect the work the database does?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

CREATE TABLE Employees (
  EmployeeID INT PRIMARY KEY,
  FirstName VARCHAR(50),
  LastName VARCHAR(50),
  Email VARCHAR(100),
  HireDate DATE
);

This code creates a table named Employees with five columns and a primary key constraint.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The database processes each column and constraint one by one.
• How many times: Once for each column and constraint defined in the table.

How Execution Grows With Input

As you add more columns, the database does more work to set up each column and its rules.

Input Size (number of columns)	Approx. Operations
5	5 operations
10	10 operations
100	100 operations

Pattern observation: The work grows directly with the number of columns; doubling columns doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to create the table grows linearly with the number of columns and constraints.

Common Mistake

[X] Wrong: "Creating a table always takes the same time no matter how many columns it has."

[OK] Correct: Each column adds work for the database to set up, so more columns mean more time.

Interview Connect

Understanding how table creation time grows helps you design databases that scale well and avoid surprises.

Self-Check

"What if we added many constraints like foreign keys and indexes? How would the time complexity change?"

Practice

1. What does the CREATE TABLE statement do in SQL?

easy

A. It deletes an existing table.

B. It selects data from a table.

C. It updates data inside a table.

D. It creates a new table in the database.

Solution

1. Step 1: Understand the purpose of CREATE TABLE

   The CREATE TABLE command is used to make a new table to store data in a database.

2. Step 2: Compare with other SQL commands

   Deleting, updating, or selecting data are done by other commands like DROP, UPDATE, and SELECT.

3. Final Answer:

   It creates a new table in the database. -> Option D

4. Quick Check:

   CREATE TABLE = create new table [OK]

Hint: Remember: CREATE TABLE makes new tables [OK]

Common Mistakes:

• Confusing CREATE with DROP or SELECT
• Thinking CREATE modifies data inside tables
• Mixing CREATE TABLE with UPDATE command

2. Which of the following is the correct syntax to create a table named Students with columns id (integer) and name (text)?

easy

A. CREATE TABLE Students (id INT, name TEXT);

B. CREATE Students TABLE (id INT, name TEXT);

C. CREATE TABLE Students id INT, name TEXT;

D. CREATE TABLE Students {id INT, name TEXT};

Solution

1. Step 1: Check the correct order of keywords

   The correct order is CREATE TABLE table_name (columns);. CREATE TABLE Students (id INT, name TEXT); follows this.

2. Step 2: Verify column definitions and punctuation

   Columns must be inside parentheses and separated by commas. CREATE TABLE Students (id INT, name TEXT); uses parentheses and commas correctly.

3. Final Answer:

   CREATE TABLE Students (id INT, name TEXT); -> Option A

4. Quick Check:

   CREATE TABLE + (columns) syntax = CREATE TABLE Students (id INT, name TEXT); [OK]

Hint: Use parentheses around columns after table name [OK]

Common Mistakes:

• Placing TABLE keyword after table name
• Missing parentheses around columns
• Using curly braces instead of parentheses

3. What will happen if you run this SQL statement?

CREATE TABLE Employees (emp_id INT PRIMARY KEY, emp_name VARCHAR(50));

medium

A. Creates a table Employees with emp_id as unique key and emp_name as text.

B. Creates a table Employees but emp_id is not unique.

C. Syntax error because VARCHAR is not allowed.

D. Creates a table Employees but emp_name cannot store text.

Solution

1. Step 1: Understand column definitions

   The statement defines emp_id as an integer and sets it as PRIMARY KEY, which means it must be unique.

2. Step 2: Check data types and constraints

   VARCHAR(50) is a valid type for text up to 50 characters. So emp_name can store text.

3. Final Answer:

   Creates a table Employees with emp_id as unique key and emp_name as text. -> Option A

4. Quick Check:

   PRIMARY KEY = unique key, VARCHAR = text [OK]

Hint: PRIMARY KEY means unique; VARCHAR stores text [OK]

Common Mistakes:

• Thinking VARCHAR is invalid
• Assuming PRIMARY KEY allows duplicates
• Confusing data types with constraints

4. Identify the error in this SQL statement:

CREATE TABLE Orders order_id INT, order_date DATE;

medium

A. Incorrect data type for order_date.

B. Missing parentheses around column definitions.

C. Table name cannot be Orders.

D. Missing semicolon at the end.

Solution

1. Step 1: Check syntax for column definitions

   Column names and types must be inside parentheses after the table name.

2. Step 2: Verify other parts

   Data types and table name are valid, and semicolon is present.

3. Final Answer:

   Missing parentheses around column definitions. -> Option B

4. Quick Check:

   Columns must be inside ( ) [OK]

Hint: Always use parentheses around columns in CREATE TABLE [OK]

Common Mistakes:

• Omitting parentheses around columns
• Using wrong data types without error
• Confusing table name rules

5. You want to create a table Products with columns product_id (integer, unique), product_name (text), and price (decimal). Which SQL statement correctly enforces uniqueness on product_id using PRIMARY KEY?

hard

A. CREATE TABLE Products (product_id INT UNIQUE, product_name TEXT, price DECIMAL);

B. CREATE TABLE Products (product_id INT, product_name TEXT, price DECIMAL UNIQUE);

C. CREATE TABLE Products (product_id INT PRIMARY KEY, product_name TEXT, price DECIMAL);

D. CREATE TABLE Products (product_id INT, product_name TEXT UNIQUE, price DECIMAL);

Solution

1. Step 1: Understand uniqueness constraints

   Both UNIQUE and PRIMARY KEY enforce uniqueness, but PRIMARY KEY also disallows NULLs and is preferred for IDs.

2. Step 2: Analyze options for correct uniqueness on product_id

   CREATE TABLE Products (product_id INT UNIQUE, product_name TEXT, price DECIMAL); uses UNIQUE on product_id, which works but PRIMARY KEY is better. CREATE TABLE Products (product_id INT PRIMARY KEY, product_name TEXT, price DECIMAL); uses PRIMARY KEY on product_id, which is the best practice.

3. Final Answer:

   CREATE TABLE Products (product_id INT PRIMARY KEY, product_name TEXT, price DECIMAL); -> Option C

4. Quick Check:

   PRIMARY KEY = unique + not null [OK]

Hint: Use PRIMARY KEY for unique IDs [OK]

Common Mistakes:

• Putting UNIQUE on wrong column
• Confusing UNIQUE with PRIMARY KEY
• Not enforcing uniqueness on ID column