Why databases over files in SQL - Performance Analysis

Time Complexity: Why databases over files

O(n)

Understanding Time Complexity

We want to understand why using databases is often faster than using simple files for storing and retrieving data.

How does the time to find or update data grow as the amount of data grows?

Scenario Under Consideration

Analyze the time complexity of searching data in a file versus a database.

-- Searching a record in a file (conceptual)
-- This represents scanning a file line by line
-- Not actual SQL syntax for file search

-- Searching a record in a database table with an index
SELECT * FROM users WHERE id = 123;

The first is like scanning a file line by line. The second uses a database index to find data quickly.

Identify Repeating Operations

Look at what repeats when searching data.

• Primary operation: Checking each record one by one in the file search.
• How many times: As many as the number of records (n) in the file.

In the database with an index, the search jumps directly to the record without checking all.

How Execution Grows With Input

As the file grows, searching takes longer because it checks more records.

Input Size (n)	Approx. Operations (File Search)
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The time grows directly with the number of records.

For the database with an index, the search time grows much slower, jumping quickly to the result.

Final Time Complexity

Time Complexity: O(n) for file search, O(log n) for database index search

This means searching in a file takes longer as data grows, but a database can find data much faster even when data is large.

Common Mistake

[X] Wrong: "Searching a file is always just as fast as a database because both store data."

[OK] Correct: Files usually require checking each record one by one, while databases use smart ways like indexes to jump directly to the data.

Interview Connect

Understanding how data search time grows helps you explain why databases are preferred for large data, showing you know practical efficiency.

Self-Check

"What if the file was sorted? How would that change the time complexity of searching in the file?"

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