Why databases over files in SQL - Quick Recap

Recall & Review

beginner

What is one main advantage of using databases instead of plain files for storing data?

Databases allow easy searching, sorting, and filtering of data, which is difficult and slow with plain files.

beginner

How do databases help with multiple users accessing data compared to files?

Databases manage multiple users safely at the same time, preventing data conflicts, while files can get corrupted if many users write at once.

intermediate

Why is data consistency easier to maintain in databases than in files?

Databases use transactions to ensure data changes are complete and correct, avoiding partial updates that can happen with files.

intermediate

What feature of databases helps recover data after a crash that files usually lack?

Databases have backup and recovery tools that can restore data to a consistent state after failures, unlike simple files.

beginner

How do databases improve data organization compared to files?

Databases store data in structured tables with relationships, making it easier to organize and connect data than flat files.

Which of the following is a key reason to use a database over a file for data storage?

A Databases allow multiple users to access data safely at the same time.

B Files are faster to search than databases.

C Files automatically prevent data corruption.

D Databases cannot handle large amounts of data.

Databases are designed to handle multiple users safely, while files can get corrupted if accessed by many users simultaneously.

What does a database use to ensure data changes are complete and correct?

A File locks

B Transactions

C Manual editing

D Backup copies

Transactions in databases ensure that data changes happen fully or not at all, maintaining consistency.

Which feature helps databases recover data after a crash?

A Manual file copying

B File compression

C Backup and recovery tools

D Simple text format

Databases include backup and recovery tools to restore data after failures.

How is data organized in a database compared to files?

A As plain text only

B Without any structure

C In random order

D In structured tables with relationships

Databases organize data in tables with defined relationships, making data easier to manage.

Why might searching data be faster in a database than in a file?

A Databases use indexes to speed up searches.

B Files are always encrypted.

C Files have built-in search engines.

D Databases store data as plain text.

Databases create indexes that allow quick searching, unlike plain files.

Explain why databases are preferred over files for managing data in applications.

Think about how many people use the data and how the data stays correct and safe.

Describe how data organization differs between databases and files.

Consider how data is stored and connected.

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