Database

Managemen
t
 So what is
Database
Management?
Database Management is the process of
storing, organizing, and handling data
effectively. Think of it like managing a large
digital library where the books are pieces of
information. Instead of shelves and books,
we have databases and data.
To keep this library
organized, we use
special software called
a Database
Management System
(DBMS)—like MySQL,
Oracle, or MongoDB.
MySQL: A popular, easy-to-
use system for organizing
data in tables (like a
spreadsheet). Great for
websites and apps.
Oracle: A powerful,
advanced system used by
big companies to handle
large amounts of data
securely and efficiently.
MongoDB: A flexible system
that stores data like digital
"notes" instead of tables,
making it great for handling
messy or changing information
(used in apps and social
media).
 So how does DBMS helps you?

01 02 03 04 05
Store data Organize Retrieve Update Protect
safely data neatly data data when data from
so it's easy quickly changes are unauthorize
to find when required d access
needed
 Data Integrity:
Key features of Ensures the
Security: Protects
data from being
DBMS information is
accessed by the
accurate and
wrong people
reliable

Backup &
Scalability: Can
Recovery: Keeps a
handle more data
copy of the data in
as the organization
case of system
grows
failures
 Database
Design &
Normalization
 What is Database
Design?

Database Design is the

process of creating a structured
framework to organize, store,
and manage data efficiently in
a database. It ensures that data
is logically organized, easy to
retrieve, and maintainable.
 Key Steps in Database
design:

•Requirement Analysis: Understand what data needs to

be stored and how it will be used.
•Conceptual Design: Create an Entity-Relationship
(ER) Diagram to model data entities, relationships, and
attributes.
•Logical Design: Define tables, columns, primary keys,
and foreign keys without focusing on the specific DBMS.
•Physical Design: Optimize the database for performance,
considering indexing, partitioning, and storage structures.
 Core Components:

•Entities: Objects or things (e.g., Customer,

Order).
•Attributes: Properties of entities (e.g.,
Name, Email).
•Relationships: How entities are related
(e.g., Customer places an Order).
 What is
Normalization?

Normalization is the process

of organizing data in a
database to reduce redundancy
and improve data integrity. It
involves breaking down large
tables into smaller, related
tables.
 Goals of normalization:

1 2 3
Eliminate Data Ensure Data Simplify Data
Redundancy: Avoid Integrity: Maintain Maintenance:
duplicate data. accuracy and Easier to update,
consistency. insert, or delete data
without anomalies.
 Normalization forms (Normal forms)

Normalization is done in stages called Normal Forms (NF):

• 1NF (First Normal Form):
• Data is in tabular format with rows and columns.
• Each cell contains a single value (no multi-valued attributes).
• Example: Splitting comma-separated values into separate rows.
• 2NF (Second Normal Form):
• Meets all 1NF requirements.
• Removes partial dependency (non-key attributes fully depend on the whole primary key).
• Mainly applies to tables with composite keys.
• 3NF (Third Normal Form):
• Meets all 2NF requirements.
• Removes transitive dependency (non-key attributes should depend only on the primary key).
• Example: Separating employee department details into a different table.
• BCNF (Boyce-Codd Normal Form):
• A stricter version of 3NF.
• Every determinant is a candidate key.
• 4NF & 5NF:
• Handle more complex relationships, like multi-valued dependencies and join dependencies.
• Rarely used unless dealing with complex data structures.
OrderI
D
CustomerNam
e
Products Example:
Normalization in
Pen,
1 Alice
Notebook Action
2 Bob Pencil

Unnormalized Table (UNF):

•Issues: Multiple products in
OrderI CustomerNam
Products one field → data redundancy.
D e

1 Alice Pen,
1NF (First Normal Form):
Notebook •Each product gets its own row.
1 Alice

2 Bob Pencil
 Customers Table: CUSTOMERID CUSTOMERNAME

2NF (Second Normal 101 Alice

Form): 102 Bob
Orders Table: Orders Table: ORDERID CUSTOMERID
Customers Table:
1 101
OrderDetails Table:
2 102

OrderDetails Table: ORDERID PRODUCT

•Data redundancy 1 Pen

reduced, relationships 1 Notebook
clarified.
2 Pencil
 Implementing
and
Querying Databases
What is Implementing
or Database
Implementation?

Database Implementation
is the process of creating
and setting up a database
based on the design, making
it ready to store, manage,
and retrieve data effectively.
 Choosing Choosing a DBMS:
Select a database system like
MySQL, PostgreSQL, MongoDB,
or SQL Server depending on the
project needs.

Use Database Creation:

Use commands like CREATE
DATABASE to set up a new
database.

Key steps in Defining Defining Tables (Schema):

Create tables with CREATE
TABLE, specifying:
Columns (fields like name, email)

Data Types (e.g., INT, VARCHAR, DATE)

Database
Constraints (e.g., PRIMARY KEY, FOREIGN
KEY, UNIQUE)

Inserting Inserting Data:

Add data using INSERT INTO
statements.

Implementati Setting Setting Indexes:

Create indexes to speed up
data retrieval.

on? Implementin
g
Implementing Security:
Set user permissions to control
access (GRANT, REVOKE).

Implement Backup & Recovery:

Implement strategies to back
up and restore data to prevent
data loss.
 What is Querying
Databases?

Querying Databases means using

specific commands to retrieve,
update, delete, or insert data from
the database. This is done using SQL
(Structured Query Language) in
relational databases or query
languages like MongoDB Query
Language for NoSQL databases.
 Data Integrity
and
Data Consistency
 What is Data
Integrity?

Data Integrity refers to the

accuracy, completeness, and
reliability of data throughout
its lifecycle. It ensures that
data remains correct,
unaltered, and consistent,
even after operations like
updates, transfers, or
processing.
 Entity Integrity:

Key types of Ensures each table has a unique identifier, usually a Primary Key.

Data Integrity: Example: Every customer in a database has a unique CustomerID.

Referential Integrity:

Maintains valid relationships between tables using Foreign Keys.

Example: An Order must reference a valid CustomerID in the Customers

table.

Domain Integrity:

Ensures that data values fall within a defined range or format.

Example: A DateOfBirth field must contain valid date values, not text like
"abc".

User-Defined Integrity:

Custom business rules that ensure data validity.

Example: A discount cannot exceed 50% unless approved by a manager.

 Constraints
: PRIMARY Validation
KEY, Rules:

How is Data FOREIGN

KEY, NOT
NULL,
Enforce data
formats and
acceptable
Integrity CHECK,
UNIQUE
ranges.

maintained Triggers:
Automated
Access
Controls:
Restrict
? actions when
data is
unauthorized
data
modified.
changes.
 Data Consistency ensures
that data remains uniform and
logically coherent across the
What is Data
database after any transaction.
Consistency?
When data is consistent, all
views of the data reflect the
same values.
 Transactional
Consistency (ACID
Model):
Key • Atomicity: Transactions are all-or-
nothing.
• Consistency: Transactions bring
component the database from one valid state
to another.

s of Data • Isolation: Transactions don’t

interfere with each other.
• Durability: Data is permanent
Consistency after transaction completion.

: Replication Consistency
(Distributed Databases):
• Ensures data copies (replicas) are
synchronized across different
servers.
 The difference
Data Integrity: between Data
•Ensures Account A and Account B exist (entity
integrity).
Integrity and Data
•Confirms that balances are valid numbers, Consistency:
not text (domain integrity).

Scenario: Online
Banking Transfer
Data Consistency:
•If $100 is deducted from Account A, the same • Step 1: You transfer
amount must be added to Account B to keep $100 from Account A to
the total balance consistent.
Account B.
 Key
differences:
Aspect Data Integrity Data Consistency

Accuracy, validity, and

Focus Uniformity and logical coherence
completeness

Individual data entries and Entire database state after

Scope
relationships transactions

Ensured Transaction management (ACID

Constraints, rules, validation
By properties)

No duplicate IDs, valid email No mismatch in account balances

Example
formats after transfers
THANK YOU FOR
LISTENING!!

Feel free to ask any questions!