Why the relational model dominates databases in DBMS Theory - Performance Analysis

Time Complexity: Why the relational model dominates databases

O(n)

Understanding Time Complexity

We want to understand how the relational model handles data operations as the amount of data grows.

How does the time to perform common tasks change when the database gets bigger?

Scenario Under Consideration

Analyze the time complexity of a simple SQL query on a relational database.

SELECT * FROM Employees WHERE Department = 'Sales';
    

This query retrieves all employees who work in the Sales department from a table.

Identify Repeating Operations

Look at what the database does to find matching rows.

• Primary operation: Scanning rows to check the Department value.
• How many times: Once for each row in the Employees table.

How Execution Grows With Input

As the number of employees grows, the database checks more rows.

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

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to find matching rows grows in a straight line as the table gets bigger.

Common Mistake

[X] Wrong: "The database instantly finds the rows no matter how big the table is."

[OK] Correct: Without special help like indexes, the database must check each row one by one, so bigger tables take more time.

Interview Connect

Understanding how queries scale with data size shows you know what affects database speed and helps you design better systems.

Self-Check

"What if we added an index on the Department column? How would the time complexity change?"

Practice

1. Why is the relational model widely used in databases?

easy

A. Because it only supports unstructured data

B. Because it organizes data in tables with rows and columns

C. Because it uses complex graphs for data storage

D. Because it stores data as plain text files

Solution

1. Step 1: Understand the structure of the relational model

   The relational model organizes data into tables, which have rows and columns, making data easy to read and manage.

2. Step 2: Compare with other data storage methods

   Unlike plain text files or graphs, tables provide a clear and simple way to store and access data.

3. Final Answer:

   Because it organizes data in tables with rows and columns -> Option B

4. Quick Check:

   Relational model = tables with rows and columns [OK]

Hint: Relational means tables with rows and columns [OK]

Common Mistakes:

• Confusing relational model with file storage
• Thinking relational model uses graphs
• Assuming it only stores unstructured data

2. Which of the following is the correct way to describe a table in the relational model?

easy

A. A set of rows and columns with unique keys

B. A collection of unordered data blobs

C. A list of files stored in folders

D. A network of connected nodes without structure

Solution

1. Step 1: Identify the relational table structure

   A relational table consists of rows (records) and columns (fields), with unique keys to identify each row.

2. Step 2: Eliminate incorrect descriptions

   Data blobs, file lists, and unstructured networks do not describe relational tables.

3. Final Answer:

   A set of rows and columns with unique keys -> Option A

4. Quick Check:

   Relational table = rows + columns + unique keys [OK]

Hint: Tables have rows, columns, and unique keys [OK]

Common Mistakes:

• Thinking tables are unordered blobs
• Confusing files with tables
• Ignoring the role of unique keys

3. Consider a database using the relational model. What happens if you try to insert a duplicate value in a column defined as a primary key?

medium

A. The database accepts the duplicate without error

B. The database deletes the existing row with the duplicate

C. The database automatically changes the duplicate value

D. The database rejects the duplicate and shows an error

Solution

1. Step 1: Understand the role of primary keys

   Primary keys uniquely identify each row in a table and must not have duplicates.

2. Step 2: Predict database behavior on duplicate insertion

   When a duplicate primary key is inserted, the database rejects it and returns an error to maintain data integrity.

3. Final Answer:

   The database rejects the duplicate and shows an error -> Option D

4. Quick Check:

   Primary key duplicates cause errors [OK]

Hint: Primary keys must be unique; duplicates cause errors [OK]

Common Mistakes:

• Assuming duplicates are allowed in primary keys
• Thinking database auto-fixes duplicates
• Believing duplicates delete existing rows

4. A developer wrote this SQL command to create a table:

CREATE TABLE Students (ID INT, Name VARCHAR(50));

Why might this table design cause problems in a relational database?

medium

A. Because it does not specify a primary key

B. Because the data types are incorrect

C. Because the table name is too long

D. Because it uses VARCHAR instead of TEXT

Solution

1. Step 1: Check table design requirements

   Relational tables should have a primary key to uniquely identify each row.

2. Step 2: Analyze the given SQL command

   The command creates a table without defining any primary key, which can cause issues with data uniqueness and integrity.

3. Final Answer:

   Because it does not specify a primary key -> Option A

4. Quick Check:

   Missing primary key causes relational issues [OK]

Hint: Always define a primary key in relational tables [OK]

Common Mistakes:

• Ignoring the need for a primary key
• Thinking VARCHAR is invalid here
• Assuming table name length matters

5. A company wants to ensure their database keeps data accurate and easy to update. Which feature of the relational model helps achieve this best?

hard

A. Using random data storage without structure

B. Storing all data as large text files

C. Use of tables with defined relationships and constraints

D. Allowing duplicate keys for faster inserts

Solution

1. Step 1: Identify key relational model features

   The relational model uses tables with relationships and constraints like primary keys and foreign keys to keep data accurate and consistent.

2. Step 2: Evaluate options for data accuracy and update ease

   Structured tables with constraints prevent errors and make updates safe, unlike unstructured or duplicate data storage.

3. Final Answer:

   Use of tables with defined relationships and constraints -> Option C

4. Quick Check:

   Relationships and constraints ensure accuracy [OK]

Hint: Relationships and constraints keep data accurate [OK]

Common Mistakes:

• Thinking unstructured storage is better
• Allowing duplicates for speed
• Ignoring constraints importance