Views for security and abstraction in SQL - Time & Space Complexity

Time Complexity: Views for security and abstraction

O(n)

Understanding Time Complexity

When using views in databases, it's important to understand how the time to get results changes as data grows.

We want to know how the database handles queries on views as the underlying tables get bigger.

Scenario Under Consideration

Analyze the time complexity of this view query.

CREATE VIEW EmployeeNames AS
SELECT EmployeeID, FirstName, LastName
FROM Employees
WHERE Active = 1;

SELECT * FROM EmployeeNames WHERE LastName = 'Smith';
    

This view shows active employees' names. The query fetches all active employees named 'Smith'.

Identify Repeating Operations

Look at what repeats when the query runs.

• Primary operation: Scanning the Employees table rows to find active employees.
• How many times: Once per query, but it checks each row in the Employees table.

How Execution Grows With Input

As the Employees table grows, the work to find matching rows grows too.

Input Size (n)	Approx. Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The number of operations grows roughly in direct proportion to the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to get results grows linearly with the number of rows in the Employees table.

Common Mistake

[X] Wrong: "Using a view makes queries instantly faster regardless of data size."

[OK] Correct: Views are saved queries, not stored results. The database still processes the underlying data each time, so bigger tables mean more work.

Interview Connect

Understanding how views affect query time helps you explain database design choices clearly and confidently in interviews.

Self-Check

What if we added an index on the LastName column? How would the time complexity change?

Practice

1. What is the main purpose of using a VIEW in SQL?

easy

A. To permanently store data in the database

B. To provide a simplified and secure way to access specific data

C. To create a backup of the database

D. To speed up the database server hardware

Solution

1. Step 1: Understand what a VIEW is

   A VIEW is a virtual table created by a SELECT query that shows data without storing it separately.

2. Step 2: Identify the purpose of a VIEW

   It helps users see only the data they need, hiding sensitive details and simplifying complex queries.

3. Final Answer:

   To provide a simplified and secure way to access specific data -> Option B

4. Quick Check:

   VIEW = Simplify + Secure access [OK]

Hint: Views show selected data safely without storing it separately [OK]

Common Mistakes:

• Thinking views store data permanently
• Confusing views with backups
• Believing views improve hardware speed

2. Which of the following is the correct syntax to create a view named EmployeeView showing only EmployeeID and Name from Employees table?

easy

A. CREATE VIEW EmployeeView AS SELECT EmployeeID, Name FROM Employees;

B. MAKE VIEW EmployeeView SELECT EmployeeID, Name FROM Employees;

C. CREATE TABLE EmployeeView AS SELECT EmployeeID, Name FROM Employees;

D. VIEW CREATE EmployeeView SELECT EmployeeID, Name FROM Employees;

Solution

1. Step 1: Recall the correct SQL syntax for creating a view

   The syntax is: CREATE VIEW view_name AS SELECT columns FROM table;

2. Step 2: Match the syntax with options

   CREATE VIEW EmployeeView AS SELECT EmployeeID, Name FROM Employees; matches the correct syntax exactly.

3. Final Answer:

   CREATE VIEW EmployeeView AS SELECT EmployeeID, Name FROM Employees; -> Option A

4. Quick Check:

   CREATE VIEW ... AS SELECT ... [OK]

Hint: Use CREATE VIEW ... AS SELECT ... to define views [OK]

Common Mistakes:

• Using MAKE VIEW instead of CREATE VIEW
• Confusing CREATE VIEW with CREATE TABLE
• Incorrect keyword order

3. Given the table Employees with columns EmployeeID, Name, Salary, and a view EmployeeView defined as:

CREATE VIEW EmployeeView AS SELECT EmployeeID, Name FROM Employees;

What will the query SELECT * FROM EmployeeView; return?

medium

A. Only Salary column

B. All columns: EmployeeID, Name, Salary

C. Only EmployeeID and Name columns

D. Syntax error because Salary is missing

Solution

1. Step 1: Understand the view definition

   The view selects only EmployeeID and Name columns from Employees.

2. Step 2: Determine what SELECT * from the view returns

   It returns only the columns defined in the view, which are EmployeeID and Name.

3. Final Answer:

   Only EmployeeID and Name columns -> Option C

4. Quick Check:

   View columns = Selected columns only [OK]

Hint: View shows only columns defined in its SELECT query [OK]

Common Mistakes:

• Expecting all original table columns
• Thinking missing columns cause syntax errors
• Confusing view columns with table columns

4. Consider this incorrect SQL statement to create a view:

CREATE VIEW SalesView SELECT OrderID, Amount FROM Sales;

What is the error and how to fix it?

medium

A. Incorrect view name; fix by renaming view

B. Missing FROM keyword; fix by adding FROM before Sales

C. SELECT statement is not allowed in views

D. Missing AS keyword; fix by adding AS after view name

Solution

1. Step 1: Identify the syntax error in CREATE VIEW

   The correct syntax requires AS keyword after the view name.

2. Step 2: Correct the statement

   Add AS after SalesView: CREATE VIEW SalesView AS SELECT OrderID, Amount FROM Sales;

3. Final Answer:

   Missing AS keyword; fix by adding AS after view name -> Option D

4. Quick Check:

   CREATE VIEW ... AS SELECT ... [OK]

Hint: Always use AS after view name in CREATE VIEW [OK]

Common Mistakes:

• Omitting AS keyword
• Misplacing FROM keyword
• Thinking SELECT is disallowed in views

5. You want to create a view PublicEmployeeData that hides the Salary column from the Employees table but allows users to see EmployeeID, Name, and Department. Which SQL statement correctly creates this view and ensures security by restricting access to sensitive data?

hard

A. CREATE VIEW PublicEmployeeData AS SELECT EmployeeID, Name, Department FROM Employees;

B. CREATE VIEW PublicEmployeeData AS SELECT * FROM Employees WHERE Salary IS NULL;

C. CREATE VIEW PublicEmployeeData AS SELECT EmployeeID, Name, Department, Salary FROM Employees;

D. CREATE VIEW PublicEmployeeData AS SELECT EmployeeID, Name FROM Employees;

Solution

1. Step 1: Identify columns to include and exclude

   We want EmployeeID, Name, Department but NOT Salary to protect sensitive data.

2. Step 2: Choose the correct SELECT statement for the view

   CREATE VIEW PublicEmployeeData AS SELECT EmployeeID, Name, Department FROM Employees; selects only the allowed columns, hiding Salary effectively.

3. Final Answer:

   CREATE VIEW PublicEmployeeData AS SELECT EmployeeID, Name, Department FROM Employees; -> Option A

4. Quick Check:

   View excludes Salary to secure sensitive data [OK]

Hint: Select only non-sensitive columns in view to protect data [OK]

Common Mistakes:

• Including Salary column accidentally
• Using WHERE Salary IS NULL which filters rows, not columns
• Selecting too few columns missing Department