CSC 111 (INTRODUCTION TO DATABASE CONCEPTS & APPLICATION)

COURSE OUTLINE: -

1. Introduction to Databases

 Definition and purpose of databases

 Evolution of database systems

 Types of databases (relational, NoSQL, etc.)

 Database management system (DBMS) overview

2. Relational Database Concepts

 Tables, records, and fields

 Keys (primary, foreign)

 Relationships (one-to-one, one-to-many, many-to-many)

 Entity-Relationship Diagrams (ERD)

3. Database Design

 Normalization (1NF, 2NF, 3NF)

 Denormalization

 Database design process

4. Structured Query Language (SQL)

 Basic SQL commands (SELECT, INSERT, UPDATE, DELETE)

 Filtering and sorting data

 Joins and subqueries

 Aggregate functions

5. Database Management

 Creating and modifying database structures

1
  Transaction management

 Data integrity and constraints

 Indexing and optimization

6. Applications of Databases

 Databases in business and industry

 Data warehousing and data mining

 Geographic Information Systems (GIS)

 Big Data and NoSQL databases

7. Final Project

 Design and implement a database

 Present and demonstrate the project

INTRODUCTION TO DATABASES

1. DEFINITION AND PURPOSE OF DATABASES:

A database is a structured collection of data organized in a way that a computer program can

quickly select and retrieve desired pieces of information. Databases are designed to manage

and store large amounts of information efficiently. The primary purpose of databases is to

provide a systematic and organized approach to storing, managing, and retrieving data,

ensuring data integrity, security, and ease of access.

2. Evolution of Database Systems:

The evolution of database systems can be traced through various stages, each marked by

technological advancements and changing requirements:

2
  File-Based Systems: Early computer systems relied on flat file structures to store and

retrieve data. This approach had limitations in terms of data redundancy and

consistency.

 Hierarchical and Network Databases: Hierarchical and network databases were

developed to address some of the limitations of file-based systems. These models

introduced relationships between data entities, allowing for more complex data

structures.

 Relational Databases: In the 1970s, Edgar F. Codd introduced the relational model,

which revolutionized database management. Relational databases organize data into

tables with rows and columns, simplifying data manipulation and retrieval.

 Object-Oriented Databases: With the rise of object-oriented programming, databases

were developed to handle complex data structures and relationships more effectively.

Object-oriented databases store data as objects, with attributes and methods.

 NoSQL Databases: As the demand for handling large volumes of unstructured and

semi-structured data grew, NoSQL (Not Only SQL) databases emerged. These

databases are designed to be more flexible and scalable than traditional relational

databases.

3. Types of Databases (Relational, NoSQL, etc.):

 Relational Databases:

 Organize data into tables with predefined schema.

 Use SQL (Structured Query Language) for querying and manipulation.

 Ensure data consistency through normalization.

 NoSQL Databases:

3
  Accommodate unstructured and diverse data types.

 Offer flexibility in data models (document-oriented, key-value, graph, etc.).

 Scale horizontally to handle large volumes of data.

 Object-Oriented Databases:

 Represent data as objects, similar to object-oriented programming.

 Store complex data structures with relationships.

 Graph Databases:

 Focus on representing and querying relationships between data entities.

 Ideal for scenarios involving complex network structures.

4. Database Management System (DBMS) Overview:

A Database Management System (DBMS) is software that facilitates database creation,

organization, and management. It acts as an intermediary between the database and the end-

user or application. Key features of DBMS include:

 Data Definition Language (DDL): Allows users to define the structure of the

database, including tables, relationships, and constraints.

 Data Manipulation Language (DML): Provides commands for querying and

modifying data within the database.

 Concurrency Control: Manages multiple users' simultaneous access to the database

to maintain data consistency.

 Transaction Management: Ensures data integrity by supporting transactions, which

are sequences of one or more operations.

 Security and Authorization: Implements measures to control access to the database

and ensure data security.

4
RELATIONAL DATABASE CONCEPTS

A relational database is a type of database that organizes data into one or more tables, where

each table consists of rows and columns. The tables are related to each other based on

common fields, allowing for the establishment of relationships between data points. This

structure enables efficient storage, retrieval, and manipulation of data, using a standardized

query language such as SQL (Structured Query Language). Relational databases are widely

used in various applications and industries due to their flexibility, scalability, and ability to

enforce data integrity through constraints and relationships. Examples of relational database

management systems (RDBMS) include MySQL, PostgreSQL, Oracle, SQL Server, and

SQLite.

Terms Associated with Relational Database: -

1. Table: A collection of related data entries organized in rows and columns.

2. Row: Also known as a record, it represents a single data item in a table.

3. Column: Also known as a field, it represents a specific attribute or characteristic of

the data stored in a table.

4. Primary Key: A unique identifier for each row in a table, used to enforce entity

integrity and ensure data uniqueness.

5. Foreign Key: A field in one table that refers to the primary key in another table,

establishing a relationship between the two tables.

6. Index: A data structure that improves the speed of data retrieval operations on a

database table at the cost of additional space and slower writes.

7. Query: A request for data retrieval or manipulation from a database, typically written

in SQL (Structured Query Language).

5
 8. Normalization: The process of organizing the data in a database to reduce redundancy

and dependency, ensuring data integrity and optimizing storage.

9. Transaction: A logical unit of work performed within a database management

system, typically involving one or more database operations.

10.ACID: An acronym for Atomicity, Consistency, Isolation, and Durability,

representing the four properties of transactions in a database system.

11.View: A virtual table generated from the result of a database query, allowing users to

access and manipulate data without altering the underlying structure.

12.Stored Procedure: A precompiled and stored set of SQL statements that can be

executed by invoking its name, providing modularity and reusability in database

applications.

13.Trigger: A set of actions automatically performed by the database management

system in response to certain database events, such as data modifications.

14.Concurrency Control: The management of simultaneous access to shared data in a

database system to prevent interference and maintain data consistency.

15.Backup and Recovery: Processes and procedures for creating copies of database files

and restoring them in the event of data loss or corruption.

1. Tables, Records, and Fields:

 Tables: In a relational database, data is organized into tables. Each table represents a

specific entity or concept and consists of rows and columns. Columns are also known

as attributes, representing the characteristics of the entity, while rows contain the

actual data entries.

6
  Records: A record is a complete set of data corresponding to a single instance of an

entity. Each row in a table is a record, and it holds information about a specific

occurrence or item.

 Fields: Fields, also known as attributes or columns, define the properties or

characteristics of the data stored in a table. For example, in a "Customers" table, fields

might include "CustomerID," "Name," "Email," and "Address."

2. Keys (Primary, Foreign):

 Primary Key: A primary key is a unique identifier for each record in a table. It

ensures that each row can be uniquely identified, and no two rows have the same

primary key. The primary key is crucial for data integrity and for establishing

relationships between tables.

 Foreign Key: A foreign key is a field in a table that refers to the primary key in

another table. It creates a link between the two tables, establishing a relationship. This

relationship is fundamental for maintaining referential integrity, ensuring that values

in the foreign key match values in the corresponding primary key.

3. Relationships (One-to-One, One-to-Many, Many-to-Many):

 One-to-One Relationship: In a one-to-one relationship, each record in one table

corresponds to exactly one record in another table. This type of relationship is used

when the entities being related have a unique and singular connection.

 One-to-Many Relationship: In a one-to-many relationship, a record in one table can

be related to multiple records in another table, but each record in the second table can

only be related to one record in the first table. This common relationship represents

scenarios where one entity can have multiple related entities.

7
  Many-to-Many Relationship: In a many-to-many relationship, each record in one

table can be associated with multiple records in another table, and vice versa. To

represent this relationship, an intermediate table (junction or associative table) is used

to connect the two tables. This is often seen in complex scenarios where entities can

have multiple relationships with each other.

4. Entity-Relationship Diagrams (ERD):

 Entity-Relationship Diagram (ERD): An ERD is a visual representation of the data

model that illustrates the entities, attributes, and relationships between tables in a

database. It uses standardized symbols to represent entities (rectangles), attributes

(ovals), and relationships (diamonds, lines).

 Components of ERD:

 Entity: Represents a table in the database, usually depicting a real-world object

or concept.

 Attributes: Characteristics or properties of entities, represented as ovals

connected to entities.

 Relationships: Connections between entities, depicted by lines connecting

them, with diamonds indicating the type of relationship (one-to-one, one-to-

many, or many-to-many).

DATABASE DESIGN

Database Design is the process of defining the structure that will organize and store data in a

database system. It involves making decisions on how data will be stored, accessed, and

managed within the database, with the ultimate goal of ensuring data accuracy, efficiency,

8
and security. The database design process encompasses both the logical and physical aspects

of organizing data to meet the requirements of an application or system.

Terms associated with Database Design: -

1. Entity: A distinct object, concept, or thing about which data is stored in a database.

Entities are represented as tables in a relational database.

2. Attribute: A characteristic or property of an entity, represented as a column in a

database table.

3. Relationship: The association or connection between two or more entities in a

database, defining how they interact with each other.

4. Primary Key: A unique identifier for each record in a table, used to ensure data

integrity and enable efficient data retrieval.

5. Foreign Key: A field in one table that refers to the primary key in another table,

establishing a relationship between the two tables.

6. Normalization: The process of organizing data in a database to reduce redundancy

and dependency, ensuring data integrity and optimizing storage.

7. Denormalization: The process of intentionally adding redundancy to a database

design to improve performance by reducing the need for joins.

8. Index: A data structure that improves the speed of data retrieval operations on a

database table at the cost of additional space and slower writes.

9. Data Model: A conceptual representation of the structure and relationships of data in

a database, often depicted using diagrams such as Entity-Relationship (ER) diagrams.

10.ER Diagram: Entity-Relationship diagram, a visual representation of the entities,

attributes, and relationships in a database.

9
 11.Cardinality: The numerical relationship between two entities in a database

relationship, indicating how many instances of one entity are associated with each

instance of another entity.

12.Constraints: Rules or conditions imposed on data to enforce integrity, such as

uniqueness constraints, foreign key constraints, and check constraints.

13.Normalization Forms (1NF, 2NF, 3NF, BCNF): Different levels of normalization

are used to eliminate redundancy and dependency in database design.

14.Schema: A logical or physical structure that defines the organization of data in a

database, including tables, fields, relationships, and constraints.

15.Data Dictionary: A centralized repository of metadata that describes the structure,

definitions, and attributes of data elements in a database.

NORMALIZATION

Normalization is the process of organizing data in a database efficiently. This includes

creating tables and establishing relationships between those tables according to rules

designed both to protect the data and to make the database more flexible by eliminating

redundancy and inconsistent dependency.

Normalization typically involves dividing large tables into smaller ones and defining

relationships between them. The objective is to isolate data so that additions, deletions, and

modifications can be made in just one table and then propagated through the rest of the

database via the defined relationships.

There are several normal forms, each building on the previous one, which define the levels

of normalization. These include:

10
 1. First Normal Form (1NF): In 1NF, each table cell should contain a single, atomic

value, and there should be no repeating groups or arrays of data. This ensures that each

column represents a single attribute, and each entry in the table is indivisible.

2. Second Normal Form (2NF): 2NF builds on 1NF by ensuring that no partial

dependencies exist. All non-key attributes should be fully functionally dependent on

the entire primary key. This eliminates redundancy by breaking the table into smaller,

related tables, each serving a specific purpose.

3. Third Normal Form (3NF): 3NF extends the normalization process by removing

transitive dependencies. In a 3NF table, non-key attributes should not depend on other

non-key attributes. This further reduces redundancy and ensures data consistency.

4. Boyce-Codd Normal Form (BCNF): A further refinement of 3NF, where every

determinant is a candidate key.

5. Fourth Normal Form (4NF) and Fifth Normal Form (5NF), also known as "Domain-

Key Normal Form" (DK/NF), deal with certain types of multivalued dependencies and

join dependencies.

2. DENORMALIZATION:

Denormalization: While normalization aims to minimize redundancy and improve data

integrity, denormalization is the process of intentionally introducing redundancy for

performance optimization. Denormalization can be applied in scenarios where read

performance is critical, and the database is read-intensive. It involves merging tables and

introducing redundant data to simplify queries and speed up data retrieval.

ADVANTAGES OF DENORMALIZATION:

11
Faster Query Performance: Redundant data can reduce the need for joins, resulting in

quicker query execution.

Simplicity: Denormalized structures can simplify complex queries, making them more

intuitive and easier to write.

Considerations:

 Increased Storage: Denormalization can lead to increased storage requirements due to

duplicated data.

 Update Anomalies: Redundant data introduces the risk of update anomalies, where

changes need to be made in multiple places.

DATABASE DESIGN PROCESS

Database Design is the process of defining the structure that will organize and store data in a

database system. It involves making decisions on how data will be stored, accessed, and

managed within the database, with the ultimate goal of ensuring data accuracy, efficiency,

and security. The database design process encompasses both the logical and physical aspects

of organizing data to meet the requirements of an application or system.

The database design process involves several steps to create an efficient, well-structured

database that meets the requirements of the users and the organization. Here's a typical

outline of the process:

1. Requirements Gathering: This initial phase involves understanding the needs of the

users and the organization. It includes identifying the data to be stored, the

relationships between different data elements, and the anticipated usage patterns of the

database.

12
2. Conceptual Design: In this phase, a high-level conceptual model of the database is

created. This often involves creating an Entity-Relationship Diagram (ERD) to

represent the entities, attributes, and relationships in the system, without getting into

the specifics of implementation.

3. Logical Design: During this stage, the conceptual model is translated into a logical

model that can be implemented using a specific database management system

(DBMS). This includes defining tables, columns, data types, constraints, and

relationships between tables. Normalization techniques are often applied to ensure

data integrity and minimize redundancy.

4. Schema Refinement: Once the logical design is in place, it may undergo refinement

based on feedback from stakeholders or further analysis of requirements. This could

involve adjusting the structure of tables, adding or removing constraints, or modifying

relationships between entities.

5. Physical Design: In this phase, the logical model is translated into a physical database

schema that can be implemented on a specific DBMS platform. This involves

decisions about storage structures, indexing strategies, partitioning, and other

optimization techniques to ensure optimal performance and scalability.

6. Implementation: With the physical design finalized, the database schema is

implemented on the chosen DBMS platform. This may involve creating tables,

indexes, views, stored procedures, and other database objects according to the

specifications defined in the design phase.

7. Testing and Evaluation: The newly implemented database is thoroughly tested to

ensure that it meets the functional and performance requirements specified during the

13
 design phase. This may involve unit testing, integration testing, performance testing,

and user acceptance testing.

8. Deployment: Once testing is complete and the database is deemed ready for

production use, it is deployed to the production environment. This may involve

migrating data from existing systems, configuring access controls, and setting up

backup and recovery procedures.

9. Maintenance and Evolution: After deployment, the database will require ongoing

maintenance to address issues, optimize performance, and accommodate changes in

requirements over time. This may involve monitoring system performance, applying

patches and updates, and making enhancements to the database schema as needed.

Throughout the database design process, collaboration between database designers,

developers, and stakeholders is crucial to ensure that the resulting database meets the needs

of the organization and its users.

STRUCTURED QUERY LANGUAGE (SQL):

Structured Query Language (SQL) is a domain-specific programming language designed

for managing, manipulating, and querying relational databases. It provides a standardized

way to interact with relational database management systems (RDBMS) to create, retrieve,

update, and delete data. SQL is widely used across various industries and plays a crucial role

in data management, making it a fundamental skill for database administrators, developers,

and data analysts.

14
1. Basic SQL Commands (SELECT, INSERT, UPDATE, DELETE):

SELECT: The ‘SELECT’ statement is used to retrieve data from one or more tables. It

allows you to specify the columns you want to retrieve, apply conditions, and order the

results.

Example:

SELECT column1, column2 FROM table WHERE condition;

INSERT: The ‘INSERT’ statement is used to add new records to a table.

Example:

INSERT INTO table (column1, column2) VALUES (value1, value2);

UPDATE: The ‘UPDATE’ statement is used to modify existing records in a table.

Example:

UPDATE table SET column1 = value1 WHERE condition;

DELETE: The ‘DELETE’ statement is used to remove records from a table.

Example:

DELETE FROM table WHERE condition;

2. Filtering and Sorting Data:

 WHERE Clause: The ‘WHERE; clause is used to filter data based on specified

conditions.

Example:

SELECT column1, column2 FROM table WHERE condition;

ORDER BY Clause: The ‘ORDER BY’ clause is used to sort the result set based on one or

more columns, either in ascending (‘ASC’) or descending (‘DESC’) order.

15
Example:

SELECT column1, column2 FROM table ORDER BY column1 ASC;

3. Joins and Subqueries:

 Joins: Joins are used to combine rows from two or more tables based on a related

column between them. Common types of joins include INNER JOIN, LEFT JOIN (or

LEFT OUTER JOIN), RIGHT JOIN (or RIGHT OUTER JOIN), and FULL JOIN.

Example:

SELECT column1, column2 FROM table1 INNER JOIN table2 ON table1.column =

table2.column;

Subqueries: A subquery is a query nested within another query. It can be used within

SELECT, FROM, WHERE, and other clauses to perform operations on the result of the

subquery.

Example:

SELECT column1 FROM table WHERE column2 IN (SELECT column2 FROM

another_table WHERE condition);

4. Aggregate Functions:

 Aggregate Functions: SQL provides various aggregate functions to perform

operations on sets of values. Common aggregate functions include:

 SUM(): Calculates the sum of values.

 AVG(): Calculates the average of values.

 COUNT(): Counts the number of rows.

 MAX(): Retrieves the maximum value.

 MIN(): Retrieves the minimum value.

16
Example:

SELECT AVG(column1), COUNT(column2) FROM table WHERE condition;

KEY FEATURES AND ASPECTS OF SQL INCLUDE:

1. Data Definition Language (DDL): SQL includes commands for defining and

managing the structure of the database, such as creating and altering tables, defining

constraints, and establishing relationships between tables.

Example DDL statements:

CREATE TABLE table_name (

column1 datatype,

column2 datatype,

...

);

ALTER TABLE table_name

ADD CONSTRAINT constraint_name PRIMARY KEY (column1);

2. Data Manipulation Language (DML): SQL provides commands for manipulating

and querying data within the database. This includes retrieving data using the ‘SELECT’

statement, inserting new records with ‘INSERT’, updating existing records with an

‘UPDATE’, and deleting records with ‘DELETE’.

Example DML statements:

SELECT column1, column2 FROM table WHERE condition;

INSERT INTO table (column1, column2) VALUES (value1, value2);

17
UPDATE table SET column1 = value1 WHERE condition;

DELETE FROM table WHERE condition;

3. Data Query Language (DQL): SQL is commonly used for querying data from one or

more tables. The ‘SELECT’ statement is a powerful tool that allows users to retrieve

specific columns, filter data based on conditions, sort results, and aggregate data.

Example DQL statement:

SELECT column1, column2 FROM table WHERE condition ORDER BY column1 ASC;

Data Control Language (DCL): SQL includes commands for controlling access to data

within the database. This includes granting or revoking permissions, and ensuring data

security and integrity.

Example DCL statements:

GRANT SELECT ON table_name TO user_name;

REVOKE INSERT ON table_name FROM user_name;

Transaction Control Language (TCL): SQL provides commands for managing

transactions, ensuring that a series of related operations are completed successfully or rolled

back if an error occurs.

Example TCL statements:

COMMIT;

ROLLBACK;

18
SQL is a standardized language, and while different database management systems may have

specific variations or extensions, the core principles and syntax remain consistent. The

language's versatility makes it an essential tool for working with relational databases in

various applications and scenarios.

DATABASE MANAGEMENT

1. Definition of Database Management:

Database Management involves the efficient organization, storage, retrieval, and

manipulation of data within a database system. It encompasses a set of activities, tools, and

processes aimed at ensuring data integrity, security, and accessibility. The primary goal of

database management is to provide a structured and efficient mechanism for storing and

managing data, enabling users and applications to interact with the database in a controlled

and organized manner.

2. Creating and Modifying Database Structures:

 Creating Tables and Relationships: Database management includes creating the

fundamental structures within a database, such as tables, relationships, and constraints.

Tables define the entities, their attributes, and the relationships between them.

Example:

CREATE TABLE Employees (

EmployeeID INT PRIMARY KEY,

FirstName VARCHAR(50),

LastName VARCHAR(50),

DepartmentID INT,

FOREIGN KEY (DepartmentID) REFERENCES Departments(DepartmentID)

19
);

Modifying Structures: As the data requirements evolve, database administrators may need

to modify the database structure. This involves altering tables, adding or removing columns,

and adjusting relationships.

Example:

ALTER TABLE Employees

ADD COLUMN Email VARCHAR(100);

3. Transaction Management:

 Transactions: A transaction is a sequence of one or more operations performed as a

single unit of work. Transaction management ensures that a series of related database

operations either succeed as a whole or fail as a whole, maintaining the consistency of

the database.

Example:

BEGIN TRANSACTION;

-- SQL statements

COMMIT;

 ACID Properties: Transactions adhere to the ACID properties:

 Atomicity: Transactions are treated as atomic units, ensuring that either all

operations succeed or none at all.

20
  Consistency: Transactions bring the database from one consistent state to

another.

 Isolation: Concurrent transactions are isolated from each other to prevent

interference.

 Durability: Once a transaction is committed, its changes are permanent and

survive system failures.

4. Data Integrity and Constraints:

 Data Integrity: Data integrity ensures the accuracy and consistency of data within the

database. This involves the use of constraints to enforce rules on data.

 Constraints:

 Primary Key: Ensures the uniqueness of a column or set of columns, serving as

a unique identifier.

 Foreign Key: Establishes a relationship between tables, ensuring referential

integrity.

 Check Constraint: Enforces a condition on data values.

Example:

CREATE TABLE Orders (

OrderID INT PRIMARY KEY,

CustomerID INT,

OrderDate DATE,

FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID),

CHECK (OrderDate >= '2022-01-01')

);

21
5. Indexing and Optimization:

 Indexing: Indexes are structures that enhance the speed of data retrieval operations on

a database table. They work similarly to an index in a book, allowing the database

engine to locate data more quickly.

Example:

CREATE INDEX idx_LastName ON Employees(LastName);

 Optimization: Database management involves optimizing the performance of queries

and operations. This may include proper indexing, query optimization, and database

design considerations.

 Query Optimization: Analyzing and optimizing the SQL queries to improve their

execution efficiency, often involving the use of execution plans.

Database management is a critical aspect of information systems, ensuring the integrity,

security, and efficiency of data storage and retrieval. Proficient database management

practices contribute to the reliability and performance of applications and systems that rely

on data-driven operations.

APPLICATIONS OF DATABASES

1. Databases in Business and Industry:

 Data Storage and Retrieval: Businesses and industries use databases to store and

manage vast amounts of structured and unstructured data efficiently. This includes

customer information, product details, financial records, and more.

22
  Transaction Processing: Databases facilitate real-time transaction processing,

enabling businesses to handle day-to-day operations such as sales, inventory

management, and order processing.

 Customer Relationship Management (CRM): CRM systems utilize databases to

centralize customer data, providing insights into customer behavior, preferences, and

interactions. This aids in improving customer satisfaction and targeted marketing.

 Enterprise Resource Planning (ERP): ERP systems integrate various business

processes by utilizing a centralized database. This allows for seamless information

flow across different departments, enhancing overall organizational efficiency.

2. Data Warehousing and Data Mining:

 Data Warehousing: Organizations use data warehouses to consolidate and store data

from various sources in a structured format. This centralized repository facilitates

business intelligence and decision-making processes.

 Business Intelligence (BI): Data warehouses support BI tools, allowing organizations

to analyze historical data trends, generate reports, and make informed strategic

decisions based on comprehensive insights.

 Data Mining: Data mining involves extracting valuable patterns and knowledge from

large datasets. By utilizing advanced algorithms, organizations can discover hidden

trends, correlations, and predictive models to gain a competitive edge.

3. Geographic Information Systems (GIS):

 Spatial Data Management: GIS combines spatial data (geographical information)

with attribute data (non-spatial information) to create layered maps. Databases in GIS

23
 store, manage, and analyze geographic data, facilitating applications in urban

planning, environmental monitoring, and more.

 Location-Based Services: Databases in GIS enable the development of location-

based services, providing users with information based on their geographical location.

This is widely used in navigation apps, geotagging, and location-based marketing.

 Resource Management: GIS databases are utilized in managing and optimizing

natural resources, such as water, forestry, and agriculture, by analyzing spatial patterns

and trends.

4. Big Data and NoSQL Databases:

 Big Data: Databases play a crucial role in handling and analyzing massive volumes of

data, known as Big Data. Traditional relational databases may struggle with the scale

and variety of Big Data, leading to the adoption of specialized technologies.

 NoSQL Databases: NoSQL databases provide a flexible and scalable alternative to

traditional relational databases. They are well-suited for handling unstructured or

semi-structured data and are commonly used in applications with high data volumes

and dynamic schemas.

 Real-Time Analytics: Big Data and NoSQL databases support real-time analytics,

allowing organizations to derive insights from data as it is generated. This is

particularly valuable in areas like social media analysis, cybersecurity, and financial

trading.

24