Why Types of databases (relational, NoSQL, object-oriented) in DBMS Theory? - Purpose & Use Cases

The Big Idea

What if your data could organize itself perfectly no matter how big or messy it gets?

The Scenario

Imagine you have a huge collection of information about your friends, their hobbies, and the events you attend together. You try to keep track of all this using just paper notes or simple lists. As your circle grows, it becomes impossible to find who likes what or when the last event was.

The Problem

Using manual notes or simple lists is slow and confusing. You might lose information, make mistakes, or spend hours searching for details. It's hard to organize complex data that changes often or has many connections.

The Solution

Different types of databases help organize and find information quickly and correctly. Relational databases use tables to connect data neatly. NoSQL databases handle flexible and big data easily. Object-oriented databases store data like real-world objects, making complex info simpler to manage.

Before vs After

✗ Before

Write down friend names and hobbies on paper; search by flipping pages.

✓ After

Use a relational database with tables for friends and hobbies linked by IDs.

What It Enables

Databases let you store, organize, and retrieve large and complex information quickly and reliably, no matter how it changes.

Real Life Example

Social media platforms use different databases to manage user profiles, posts, and messages efficiently, so you see your feed instantly and can search friends easily.

Key Takeaways

Manual tracking of complex data is slow and error-prone.

Relational, NoSQL, and object-oriented databases each organize data in ways that fit different needs.

Using the right database type makes managing and finding information fast and reliable.

Practice

1. Which type of database stores data in tables and uses SQL for queries?

easy

A. Object-oriented database

B. NoSQL database

C. Graph database

D. Relational database

Solution

1. Step 1: Understand database types

   Relational databases organize data in tables with rows and columns.

2. Step 2: Identify query language

   They use SQL (Structured Query Language) to manage and query data.

3. Final Answer:

   Relational database -> Option D

4. Quick Check:

   Tables + SQL = Relational database [OK]

Hint: Tables and SQL mean relational database [OK]

Common Mistakes:

• Confusing NoSQL with relational because both store data
• Thinking object-oriented databases use SQL
• Assuming graph databases are relational

2. Which of the following is the correct way to describe a NoSQL database?

easy

A. Stores flexible data like documents or key-value pairs

B. Stores data only in tables with fixed schema

C. Stores data as objects matching programming languages

D. Uses only SQL for data queries

Solution

1. Step 1: Recall NoSQL database features

   NoSQL databases store data flexibly, often as documents or key-value pairs.

2. Step 2: Eliminate incorrect options

   They do not require fixed schemas or only tables, and do not rely solely on SQL.

3. Final Answer:

   Stores flexible data like documents or key-value pairs -> Option A

4. Quick Check:

   No fixed schema + flexible data = NoSQL [OK]

Hint: Flexible data storage means NoSQL [OK]

Common Mistakes:

• Thinking NoSQL uses only tables
• Confusing object-oriented with NoSQL
• Assuming NoSQL requires SQL queries

3. Given the following description, which database type fits best?
Data is stored as objects with properties and methods, similar to programming languages.

medium

A. Relational database

B. NoSQL database

C. Object-oriented database

D. Hierarchical database

Solution

1. Step 1: Analyze data storage style

   The data is stored as objects with properties and methods, matching programming language objects.

2. Step 2: Match to database type

   Object-oriented databases store data as objects, unlike relational or NoSQL databases.

3. Final Answer:

   Object-oriented database -> Option C

4. Quick Check:

   Objects with methods = Object-oriented database [OK]

Hint: Objects with methods mean object-oriented DB [OK]

Common Mistakes:

• Confusing object-oriented with NoSQL
• Thinking relational databases store objects
• Assuming hierarchical is object-oriented

4. Identify the error in this statement:
NoSQL databases always use SQL queries to retrieve data.

medium

A. No error, statement is correct

B. NoSQL databases do not use SQL queries

C. NoSQL databases only store data in tables

D. NoSQL databases are a type of relational database

Solution

1. Step 1: Understand NoSQL query methods

   NoSQL databases typically use query methods other than SQL, like JSON queries or key-value lookups.

2. Step 2: Identify the error

   The statement wrongly claims NoSQL always uses SQL, which is false.

3. Final Answer:

   NoSQL databases do not use SQL queries -> Option B

4. Quick Check:

   NoSQL ≠ SQL queries [OK]

Hint: NoSQL means no SQL queries [OK]

Common Mistakes:

• Believing NoSQL uses SQL
• Confusing NoSQL with relational
• Thinking NoSQL stores only tables

5. A company wants to store user profiles with flexible fields that can change often, and also wants to store some complex objects with methods for processing. Which combination of databases should they use?

hard

A. A NoSQL database for flexible data and an object-oriented database for complex objects

B. Only a relational database

C. Only a NoSQL database

D. Only an object-oriented database

Solution

1. Step 1: Analyze data needs

   Flexible fields suggest NoSQL for schema flexibility; complex objects with methods suggest object-oriented database.

2. Step 2: Choose suitable combination

   Using both NoSQL and object-oriented databases fits the requirements best.

3. Final Answer:

   A NoSQL database for flexible data and an object-oriented database for complex objects -> Option A

4. Quick Check:

   Flexible + complex objects = NoSQL + object-oriented [OK]

Hint: Use NoSQL for flexible, object-oriented for complex objects [OK]

Common Mistakes:

• Choosing only relational database ignoring flexibility
• Using only NoSQL and ignoring object methods
• Assuming object-oriented alone handles flexible fields