Why views are needed in SQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Views in Databases

Why do databases use views? Choose the best reason.

A To simplify complex queries by saving them as reusable virtual tables

B To physically store large amounts of data for faster access

C To replace indexes for speeding up data retrieval

D To permanently delete data from multiple tables at once

💡 Hint

Think about how views help users work with data without changing the original tables.

Views act like saved queries that look like tables but do not store data themselves. They help simplify complex queries and provide a consistent way to see data.

🧠 Conceptual

intermediate

Security Benefit of Views

How do views help improve database security?

A By allowing users to see only specific columns or rows without accessing the full table

B By encrypting all data stored in the database automatically

C By blocking all user access except for administrators

D By deleting sensitive data after a set time

💡 Hint

Think about how views can limit what data a user can see.

Views can show only selected parts of a table, so users can access just the data they need without seeing sensitive information.

❓ query_result

advanced

Output of Query Using a View

Given the view definition and table data below, what will this query return?

SQL

CREATE VIEW ActiveCustomers AS
SELECT CustomerID, Name FROM Customers WHERE Status = 'Active';

-- Table Customers:
-- CustomerID | Name    | Status
-- 1          | Alice   | Active
-- 2          | Bob     | Inactive
-- 3          | Carol   | Active

SELECT * FROM ActiveCustomers;

A CustomerID: 2, Name: Bob

B CustomerID: 1, Name: Alice; CustomerID: 2, Name: Bob; CustomerID: 3, Name: Carol

C CustomerID: 1, Name: Alice; CustomerID: 3, Name: Carol

D Empty result set

💡 Hint

Look at the WHERE clause in the view definition.

The view selects only customers with Status 'Active'. Bob is 'Inactive', so he is excluded.

🧠 Conceptual

advanced

Why Views Improve Maintainability

How do views help maintain database applications when the underlying tables change?

A They automatically update all application code to match table changes

B They store backup copies of tables to restore if needed

C They prevent any changes to the underlying tables

D They provide a stable interface so queries don’t need to change even if table structures do

💡 Hint

Think about how views act as a layer between users and tables.

Views can hide changes in table structure by presenting data in a consistent way, so applications using views don’t break when tables change.

🧠 Conceptual

expert

Performance Impact of Views

Which statement about the performance impact of views is true?

A Views always improve performance by caching data automatically

B Views do not store data, so querying a view runs the underlying query each time, which can affect performance

C Views create physical copies of data that speed up queries

D Views prevent the database from using indexes on underlying tables

💡 Hint

Consider what happens when you query a view.

Since views are virtual tables defined by queries, the database runs the view’s query each time it is accessed, which can slow down performance if the query is complex.

Practice

1. Why do we use views in a database?
SELECT * FROM view_name; What is the main purpose of this?

easy

A. To speed up the database server hardware

B. To permanently store data physically in the database

C. To delete data from multiple tables at once

D. To simplify complex queries by showing only needed data

Solution

1. Step 1: Understand what a view does

   A view is a saved query that shows data in a simpler way without storing data separately.

2. Step 2: Identify the main purpose of views

   Views help users see only the data they need, hiding complexity and sensitive info.

3. Final Answer:

   To simplify complex queries by showing only needed data -> Option D

4. Quick Check:

   Views simplify data = C [OK]

Hint: Views show simpler data without storing it [OK]

Common Mistakes:

• Thinking views store data physically
• Confusing views with database hardware
• Believing views delete data

2. Which of the following is the correct syntax to create a view named EmployeeView that shows only name and salary from Employees table?

easy

A. CREATE VIEW EmployeeView AS SELECT name, salary FROM Employees;

B. CREATE TABLE EmployeeView AS SELECT name, salary FROM Employees;

C. INSERT VIEW EmployeeView SELECT name, salary FROM Employees;

D. VIEW CREATE EmployeeView SELECT name, salary FROM Employees;

Solution

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

   The correct syntax starts with CREATE VIEW, then the view name, followed by AS and the SELECT query.

2. Step 2: Match the options with correct syntax

   CREATE VIEW EmployeeView AS SELECT name, salary FROM Employees; matches the correct syntax exactly; others use wrong keywords or order.

3. Final Answer:

   CREATE VIEW EmployeeView AS SELECT name, salary FROM Employees; -> Option A

4. Quick Check:

   CREATE VIEW + AS + SELECT = B [OK]

Hint: Use CREATE VIEW ... AS SELECT ... [OK]

Common Mistakes:

• Using CREATE TABLE instead of CREATE VIEW
• Wrong keyword order like INSERT VIEW
• Omitting AS keyword

3. Given the table Sales with columns product, region, and amount, and the view:
CREATE VIEW RegionalSales AS SELECT region, SUM(amount) AS total FROM Sales GROUP BY region;
What will the query SELECT * FROM RegionalSales WHERE total > 1000; return?

medium

A. All rows from Sales table without filtering

B. Rows showing regions where total sales amount is more than 1000

C. Syntax error because views cannot use GROUP BY

D. Empty result because total is not a column in Sales

Solution

1. Step 1: Understand the view definition

   The view groups sales by region and sums amounts, creating a total per region.

2. Step 2: Analyze the query on the view

   The query filters regions where total sales exceed 1000, so it returns those regions and totals.

3. Final Answer:

   Rows showing regions where total sales amount is more than 1000 -> Option B

4. Quick Check:

   View groups and filters totals > 1000 = A [OK]

Hint: Views can use GROUP BY and filters on aggregated columns [OK]

Common Mistakes:

• Thinking views cannot use GROUP BY
• Confusing view columns with base table columns
• Assuming syntax error due to alias

4. You tried to create a view with:
CREATE VIEW MyView AS SELECT id, password FROM Users;
But you want to hide the password column for security. What is the best fix?

medium

A. Remove password from the SELECT list in the view

B. Rename the view to hide the password

C. Add WHERE password IS NOT NULL clause

D. Use DELETE to remove password column from Users table

Solution

1. Step 1: Identify the problem with the view

   The view currently shows the password column, which exposes sensitive data.

2. Step 2: Fix the view to hide sensitive data

   Removing the password column from the SELECT statement prevents it from appearing in the view.

3. Final Answer:

   Remove password from the SELECT list in the view -> Option A

4. Quick Check:

   Exclude sensitive columns from view SELECT = D [OK]

Hint: Exclude sensitive columns in view SELECT to hide them [OK]

Common Mistakes:

• Trying to rename view to hide data
• Using WHERE clause to filter columns
• Deleting columns from base table instead of view

5. You want to create a view that shows only active customers with their total orders, but the Orders table has millions of rows. Which approach best uses views to improve performance and security?

hard

A. Create a view that deletes inactive customers from the database

B. Create a view selecting all customers and orders without filters

C. Create a view filtering active customers and pre-aggregating order totals

D. Create a view that stores all orders physically to speed queries

Solution

1. Step 1: Understand the goal for the view

   The view should show only active customers and their total orders to reduce data size and protect inactive data.

2. Step 2: Choose the best approach for performance and security

   Filtering and pre-aggregating in the view reduces data scanned and hides unnecessary info, improving speed and security.

3. Final Answer:

   Create a view filtering active customers and pre-aggregating order totals -> Option C

4. Quick Check:

   Filter and aggregate in view for speed and security = A [OK]

Hint: Filter and aggregate in views to improve speed and hide data [OK]

Common Mistakes:

• Selecting all data without filters
• Trying to delete data via views
• Misunderstanding views store data physically