Why SELECT specific columns in SQL? - Purpose & Use Cases

The Big Idea

What if you could instantly grab just the info you want from a sea of data?

The Scenario

Imagine you have a huge spreadsheet with thousands of rows and dozens of columns. You want to find just the names and phone numbers of your friends, but you have to scroll through every column manually to find them.

The Problem

Manually scanning through all columns is slow and tiring. You might copy the wrong data or miss important details. It's easy to get overwhelmed and make mistakes when handling so much information at once.

The Solution

Using SELECT specific columns in SQL lets you pick only the exact pieces of information you need. This saves time, reduces errors, and makes your results clear and focused.

Before vs After

✗ Before

Look through every column in the spreadsheet to find names and phones.

✓ After

SELECT name, phone FROM contacts;

What It Enables

This lets you quickly get just the data you want, making your work faster and easier.

Real Life Example

When a company wants to send a newsletter, they only need customers' email addresses and names, not their full purchase history. Selecting specific columns helps them get just that.

Key Takeaways

Manually searching all data is slow and error-prone.

SELECT specific columns picks only what you need.

This makes data handling faster and clearer.

Practice

1. What does the SQL statement SELECT name, age FROM users; do?

easy

A. It retrieves all columns from the users table.

B. It updates the name and age columns in the users table.

C. It deletes the name and age columns from the users table.

D. It retrieves only the name and age columns from the users table.

Solution

1. Step 1: Understand the SELECT clause

   The SELECT clause specifies which columns to retrieve from the table.

2. Step 2: Identify columns listed

   The columns listed are name and age, so only these will be returned.

3. Final Answer:

   It retrieves only the name and age columns from the users table. -> Option D

4. Quick Check:

   SELECT specific columns = selected columns only [OK]

Hint: SELECT lists columns to get only those columns [OK]

Common Mistakes:

• Thinking SELECT * returns specific columns
• Confusing SELECT with DELETE or UPDATE
• Not separating columns by commas

2. Which of the following is the correct syntax to select the columns 'id' and 'email' from a table named 'contacts'?

easy

A. SELECT id email FROM contacts;

B. SELECT id, email FROM contacts;

C. SELECT (id, email) FROM contacts;

D. SELECT id; email FROM contacts;

Solution

1. Step 1: Check column separation syntax

   Columns must be separated by commas without parentheses.

2. Step 2: Identify correct option

   SELECT id, email FROM contacts; uses commas correctly: SELECT id, email FROM contacts;

3. Final Answer:

   SELECT id, email FROM contacts; -> Option B

4. Quick Check:

   Columns separated by commas = correct syntax [OK]

Hint: Separate columns with commas, no parentheses [OK]

Common Mistakes:

• Omitting commas between columns
• Using parentheses around columns
• Using semicolons between columns

3. Given the table products with columns product_id, name, and price, what will be the output of this query?

SELECT name, price FROM products WHERE price < 50;

medium

A. All columns for products priced below 50

B. An error because price is not selected

C. Only the name and price columns for products priced below 50

D. Only the product_id column for products priced below 50

Solution

1. Step 1: Understand SELECT columns

   The query selects only name and price columns.

2. Step 2: Apply WHERE condition

   Only rows where price is less than 50 are included.

3. Final Answer:

   Only the name and price columns for products priced below 50 -> Option C

4. Quick Check:

   SELECT specific columns + WHERE filters rows [OK]

Hint: SELECT columns limits output columns, WHERE filters rows [OK]

Common Mistakes:

• Expecting all columns to be returned
• Thinking WHERE changes columns selected
• Assuming error if column not in SELECT

4. Identify the error in this SQL query:

SELECT name age FROM employees;

medium

A. Missing comma between columns name and age

B. Table name employees is incorrect

C. SELECT cannot be used without WHERE

D. No error, query is correct

Solution

1. Step 1: Check column separation

   Columns must be separated by commas; here name and age are not separated.

2. Step 2: Confirm table name and syntax

   Table name employees is valid and WHERE is optional.

3. Final Answer:

   Missing comma between columns name and age -> Option A

4. Quick Check:

   Columns need commas between them [OK]

Hint: Always separate columns with commas [OK]

Common Mistakes:

• Forgetting commas between columns
• Thinking WHERE is mandatory
• Assuming table name is wrong without evidence

5. You have a table orders with columns order_id, customer_id, order_date, and total. You want to list only the order_id and total for orders made in 2023. Which query is correct?

hard

A. SELECT order_id, total FROM orders WHERE order_date LIKE '2023%';

B. SELECT order_id total FROM orders WHERE order_date = 2023;

C. SELECT order_id, total FROM orders WHERE order_date = '2023';

D. SELECT * FROM orders WHERE order_date LIKE '2023%';

Solution

1. Step 1: Select specific columns

   We want only order_id and total, so SELECT order_id, total is correct.

2. Step 2: Filter orders from 2023

   Using WHERE order_date LIKE '2023%' matches dates starting with 2023.

3. Step 3: Check other options

   SELECT order_id total FROM orders WHERE order_date = 2023; misses comma and uses wrong date filter; SELECT order_id, total FROM orders WHERE order_date = '2023'; uses exact match which won't work for full dates; SELECT * FROM orders WHERE order_date LIKE '2023%'; selects all columns, not specific ones.

4. Final Answer:

   SELECT order_id, total FROM orders WHERE order_date LIKE '2023%'; -> Option A

5. Quick Check:

   Select columns + LIKE filter for year = correct query [OK]

Hint: Use LIKE '2023%' to filter year, separate columns with commas [OK]

Common Mistakes:

• Forgetting commas between columns
• Using = instead of LIKE for partial date match
• Selecting all columns instead of specific ones