Why table design affects performance in MySQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does indexing affect query speed?

Which of the following best explains why adding an index to a table column can improve query performance?

A Indexes reduce the amount of data the database scans by allowing quick lookups on the indexed column.

B Indexes duplicate the entire table, so queries run on the copy instead of the original.

C Indexes automatically compress the data, making queries faster by reducing size.

D Indexes store all table data in memory, so queries never access the disk.

💡 Hint

Think about how a phone book helps you find a name faster without reading every page.

Indexes act like a quick lookup guide, allowing the database to find rows without scanning the whole table.

❓ query_result

intermediate

Effect of data types on storage and speed

Consider a table with a column storing dates. Which data type choice will generally use less storage and improve query speed?

A Using VARCHAR(10) to store dates as text like '2024-06-01'.

B Using TEXT data type to store dates with extra formatting.

C Using DATE data type to store dates in a compact binary format.

D Using INT to store dates as Unix timestamps.

💡 Hint

Think about storing dates in a format the database understands natively.

DATE type uses fixed, compact storage and allows efficient date operations, unlike text types.

📝 Syntax

advanced

Identify the correct primary key definition

Which SQL statement correctly defines a primary key on the 'id' column during table creation?

MySQL

CREATE TABLE users (
  id INT,
  name VARCHAR(100),
  PRIMARY KEY (id)
);

A CREATE TABLE users (id INT, name VARCHAR(100), PRIMARY KEY (name));

B CREATE TABLE users (id INT, name VARCHAR(100), PRIMARY KEY id);

C CREATE TABLE users (id INT, name VARCHAR(100), PRIMARY KEY = id);

D CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(100));

💡 Hint

Primary key syntax requires parentheses around column names or inline declaration.

Option D correctly declares 'id' as primary key inline. Option D and C have syntax errors. Option D uses wrong column.

❓ optimization

advanced

Choosing between normalized and denormalized tables

Which scenario best explains when denormalizing a table can improve performance?

A When data integrity is critical, denormalization ensures no duplicate data exists.

B When frequent joins slow down queries, storing redundant data in one table reduces join operations.

C When storage space is limited, denormalization reduces data size by removing duplicates.

D When the database is small, denormalization automatically speeds up all queries.

💡 Hint

Think about how joining many tables can slow down queries.

Denormalization duplicates some data to avoid costly joins, improving read performance at the cost of storage and update complexity.

🔧 Debug

expert

Diagnosing slow query due to poor table design

A query filtering on a 'status' column is very slow on a large table. The 'status' column has only three possible values. What is the most likely cause?

A The 'status' column is indexed, but the index is ignored because it has low cardinality.

B The 'status' column is not indexed, so the database scans the entire table for matches.

C The table uses a VARCHAR type for 'status' instead of ENUM, causing slow comparisons.

D The table is normalized, so the query must join multiple tables to get 'status'.

💡 Hint

Indexes on columns with few distinct values may not be used by the database.

Low cardinality indexes (few unique values) are often ignored by the optimizer because scanning is cheaper than using the index.

Practice

1. Why does using proper data types in a MySQL table improve performance?

easy

A. It reduces the amount of storage space and speeds up data retrieval.

B. It makes the table look nicer in the database.

C. It allows more users to connect at the same time.

D. It automatically creates backups of the data.

Solution

1. Step 1: Understand data types and storage

   Choosing the right data type means the database uses only the needed space for each value.

2. Step 2: Impact on speed

   Smaller data sizes mean faster reading and writing, improving performance.

3. Final Answer:

   It reduces the amount of storage space and speeds up data retrieval. -> Option A

4. Quick Check:

   Proper data types = less space + faster queries [OK]

Hint: Smaller data types mean faster access and less storage [OK]

Common Mistakes:

• Thinking data types only affect appearance
• Believing data types control user connections
• Confusing data types with backup features

2. Which of the following is the correct way to define a primary key in a MySQL table?

easy

A. CREATE TABLE users (id INT PRIMARY KEY);

B. CREATE TABLE users (id INT PRIMARY, KEY);

C. CREATE TABLE users (id INT, PRIMARY(id));

D. CREATE TABLE users (id INT, KEY PRIMARY);

Solution

1. Step 1: Review MySQL primary key syntax

   The correct syntax places PRIMARY KEY immediately after the column type.

2. Step 2: Check each option

   CREATE TABLE users (id INT PRIMARY KEY); uses 'id INT PRIMARY KEY' which is valid syntax.

3. Final Answer:

   CREATE TABLE users (id INT PRIMARY KEY); -> Option A

4. Quick Check:

   Primary key syntax = 'column type PRIMARY KEY' [OK]

Hint: Primary key goes right after column type [OK]

Common Mistakes:

• Separating PRIMARY and KEY keywords incorrectly
• Placing KEY before PRIMARY
• Using comma incorrectly between keywords

3. Given the table products(id INT PRIMARY KEY, name VARCHAR(50), price DECIMAL(5,2)), what will be the result of this query?
SELECT * FROM products WHERE price < 10.00;

medium

A. No rows will be returned because price is stored as text.

B. Syntax error because of the decimal comparison.

C. All products with price less than 10.00 will be listed.

D. Only products with price exactly 10.00 will be shown.

Solution

1. Step 1: Understand the table schema

   The price column is DECIMAL(5,2), a numeric type suitable for decimal comparisons.

2. Step 2: Analyze the query condition

   The query selects rows where price is less than 10.00, which is valid and will return matching rows.

3. Final Answer:

   All products with price less than 10.00 will be listed. -> Option C

4. Quick Check:

   DECIMAL supports numeric comparisons correctly [OK]

Hint: DECIMAL columns compare numbers, not text [OK]

Common Mistakes:

• Assuming DECIMAL is text type
• Thinking decimal comparisons cause syntax errors
• Confusing less than with equal to

4. A table has no indexes and is very slow when searching by a column. What is the best fix?

medium

A. Use SELECT * instead of SELECT column.

B. Change the column data type to TEXT.

C. Delete half of the rows to reduce size.

D. Add an index on the column used in the search.

Solution

1. Step 1: Identify the cause of slow search

   Without indexes, MySQL must scan all rows, causing slow searches.

2. Step 2: Apply indexing to improve speed

   Adding an index on the searched column lets MySQL find rows faster.

3. Final Answer:

   Add an index on the column used in the search. -> Option D

4. Quick Check:

   Indexes speed up searches [OK]

Hint: Index columns you search often for faster queries [OK]

Common Mistakes:

• Changing data type without indexing
• Deleting data instead of optimizing
• Using SELECT * slows queries, but not main cause

5. You have a table with many duplicate rows causing slow queries and large storage. What table design change will best improve performance?

hard

A. Increase the size of all columns to store more data.

B. Add a UNIQUE constraint to prevent duplicates and clean existing data.

C. Remove all indexes to speed up inserts.

D. Change all VARCHAR columns to TEXT for flexibility.

Solution

1. Step 1: Identify the problem with duplicates

   Duplicates cause extra storage and slow queries because more rows must be scanned.

2. Step 2: Use UNIQUE constraint to fix duplicates

   Adding UNIQUE prevents duplicates and cleaning data reduces size and speeds queries.

3. Final Answer:

   Add a UNIQUE constraint to prevent duplicates and clean existing data. -> Option B

4. Quick Check:

   Unique constraints remove duplicates and improve performance [OK]

Hint: Use UNIQUE keys to avoid duplicates and speed queries [OK]

Common Mistakes:

• Thinking bigger columns improve speed
• Removing indexes slows queries
• Using TEXT instead of VARCHAR wastes space