Why databases over files in SQL - See It in Action

Why Databases Over Files

📖 Scenario: Imagine you run a small bookstore. You want to keep track of your books and sales. You could write all this information in simple text files, but it can get messy and slow as your store grows.This project will help you understand why using a database is better than just using files.

🎯 Goal: You will create a simple table to store book information, add a configuration for a minimum stock level, write a query to find books that need restocking, and finalize the setup with a primary key.

📋 What You'll Learn

Create a table called Books with columns BookID, Title, and Stock

Add a variable min_stock to set the minimum stock level

Write a query to select books where Stock is less than min_stock

Add a primary key constraint on BookID

💡 Why This Matters

🌍 Real World

Stores, libraries, and many businesses use databases to keep their data organized and easy to access instead of messy files.

💼 Career

Knowing how to create tables, set variables, and write queries is essential for database jobs and managing data efficiently.

1

Create the Books table

Write a SQL statement to create a table called Books with columns BookID as integer, Title as text, and Stock as integer.

SQL

-- Create the Books table with BookID, Title, and Stock columns
-- Your code here

Hint

Use CREATE TABLE Books (BookID INTEGER, Title TEXT, Stock INTEGER);

2

Set minimum stock level

Add a SQL variable called min_stock and set it to 5 to represent the minimum stock level.

SQL

CREATE TABLE Books (
    BookID INTEGER,
    Title TEXT,
    Stock INTEGER
);
-- Declare min_stock variable and set it to 5
-- Your code here

Hint

Use DECLARE min_stock INTEGER DEFAULT 5; to set the variable.

3

Query books needing restock

Write a SQL query to select all columns from Books where the Stock is less than the variable min_stock.

SQL

CREATE TABLE Books (
    BookID INTEGER,
    Title TEXT,
    Stock INTEGER
);

-- Set minimum stock level
DECLARE min_stock INTEGER DEFAULT 5;

-- Select books with stock less than min_stock
-- Your code here

Hint

Use SELECT * FROM Books WHERE Stock < min_stock; to find books to restock.

4

Add primary key to Books table

Modify the Books table creation statement to add a primary key constraint on the BookID column.

SQL

-- Modify the Books table to add primary key on BookID
CREATE TABLE Books (
    BookID INTEGER,
    Title TEXT,
    Stock INTEGER
);

-- Set minimum stock level
DECLARE min_stock INTEGER DEFAULT 5;

-- Query books needing restock
SELECT * FROM Books WHERE Stock < min_stock;
-- Your code here

Hint

Add PRIMARY KEY after BookID INTEGER in the table definition.

Practice

1. Why do we prefer databases over simple files for storing data?

easy

A. Databases cannot store large amounts of data.

B. Files are faster to search than databases.

C. Databases allow multiple users to access and update data safely at the same time.

D. Files automatically protect data better than databases.

Solution

1. Step 1: Understand data access needs

   Multiple users often need to read and write data simultaneously in real life, like in banks or stores.

2. Step 2: Compare files and databases

   Simple files do not handle multiple users well and can cause data loss or errors. Databases manage this safely.

3. Final Answer:

   Databases allow multiple users to access and update data safely at the same time. -> Option C

4. Quick Check:

   Multiple safe access = Databases [OK]

Hint: Databases handle many users safely, files do not [OK]

Common Mistakes:

• Thinking files are faster to search than databases
• Believing files protect data better automatically
• Assuming databases cannot store large data

2. Which of the following is the correct reason why databases are better than files?

easy

A. Databases support concurrent access with data integrity.

B. Databases do not allow data updates once saved.

C. Files automatically create backups.

D. Files can handle complex queries easily.

Solution

1. Step 1: Review database features

   Databases allow many users to access and update data at the same time without corrupting it.

2. Step 2: Check file limitations

   Files do not manage concurrent access well and do not ensure data integrity during updates.

3. Final Answer:

   Databases support concurrent access with data integrity. -> Option A

4. Quick Check:

   Concurrent safe access = Databases [OK]

Hint: Databases keep data safe when many users update [OK]

Common Mistakes:

• Believing databases prevent any data updates
• Thinking files create backups automatically
• Assuming files handle complex queries easily

3. Consider a system where multiple users try to update a customer record stored in a simple file simultaneously. What is the most likely outcome?

medium

A. All updates will be saved correctly without any data loss.

B. The system will convert the file into a database automatically.

C. The file will automatically lock and queue updates safely.

D. Some updates may overwrite others causing data loss or corruption.

Solution

1. Step 1: Understand file behavior with multiple writes

   Simple files do not manage simultaneous writes well, so one update can overwrite another.

2. Step 2: Compare with database behavior

   Databases use locks and transactions to prevent such data loss, but files lack this feature.

3. Final Answer:

   Some updates may overwrite others causing data loss or corruption. -> Option D

4. Quick Check:

   Simultaneous file writes = Data loss risk [OK]

Hint: Files lack safe multi-user update controls [OK]

Common Mistakes:

• Assuming files lock automatically
• Believing all updates save correctly
• Thinking files convert to databases automatically

4. You have a file-based system where users report data inconsistencies after simultaneous updates. What is the best fix?

medium

A. Switch to a database system that supports transactions and concurrency control.

B. Increase the file size limit to avoid data loss.

C. Allow only one user to access the file at a time manually.

D. Use a faster computer to reduce update time.

Solution

1. Step 1: Identify the cause of inconsistencies

   Simultaneous updates on files cause conflicts and data corruption due to lack of concurrency control.

2. Step 2: Choose a solution that handles concurrency

   Databases provide transactions and locking to manage multiple users safely, fixing inconsistencies.

3. Final Answer:

   Switch to a database system that supports transactions and concurrency control. -> Option A

4. Quick Check:

   Concurrency fix = Use database [OK]

Hint: Use databases for safe multi-user updates [OK]

Common Mistakes:

• Thinking increasing file size helps concurrency
• Believing manual single-user access is practical
• Assuming faster computers fix data conflicts

5. A company stores customer orders in files but faces issues with data loss and slow searches. How can switching to a database solve these problems?

hard

A. Databases delete old data automatically to save space.

B. Databases organize data in tables with indexes, speeding up searches and preventing data loss with backups and transactions.

C. Databases store data as plain text files, so no change occurs.

D. Databases require manual file locking to avoid conflicts.

Solution

1. Step 1: Identify file system problems

   Files lack indexing, making searches slow, and have no built-in backup or transaction support, risking data loss.

2. Step 2: Understand database advantages

   Databases store data in tables with indexes for fast search and use transactions and backups to protect data.

3. Final Answer:

   Databases organize data in tables with indexes, speeding up searches and preventing data loss with backups and transactions. -> Option B

4. Quick Check:

   Tables + indexes + transactions = Faster, safer data [OK]

Hint: Databases speed search and protect data with transactions [OK]

Common Mistakes:

• Thinking databases store data as plain text files
• Believing databases delete old data automatically
• Assuming manual locking is needed in databases