2.

NoSQL Databases - flexible schema

suitable for unstructured or semi-structured
data.
- designed for flexible and scalable
Review of Database Fundamentals data storage.
- MongoDB, Redis, Cassandra,
Database Firebase
- is organized collection of related data stored - Document-based (e.g.,
and managed electronically MongoDB)
- an organized collection of data stored and - Key-Value (e.g., Redis)
managed in a structured manner - Column-Family (e.g.,
- collection of organized data stored and Cassandra)
accessed electronically. - Graph (e.g., Neo4j).
3. Object-Oriented Databases - Store objects
Key Components and their relationships directly.
1. User - individuals or application that interact 4. Graph Databases - Store data in nodes
with database and edges for efficient relationship
2. Data - refers to the information stored in representation.
the database
3. Database Management System - the Data Privacy Act
software used to managed the database - Importance of securing sensitive data.
- Encryption, access controls, and regular
Importance of Databases backups to safeguard data.
1. Efficient data organization and storage. - Compliance with data protection regulations
2. Quick and reliable data access and (e.g., Republic Act 10173 - Data Privacy Act
retrieval. of 2012).
3. Support for concurrent data access by
multiple users. Data Modeling
4. Data security and integrity. - Crucial step in creating an efficient and
5. Scalability to handle large volumes of data. reliable database.
6. Crucial for business intelligence, analytics, - Key considerations: Data modeling,
and decision-making. normalization, indexing, and relationships.

Risks of Databases Database Schema

1. New specialized personnel - structured representation of data storage in
2. Need for explicit backup a database.
3. Organization Conflict - Blueprint and framework of database
4. Large Size - Defines the database structures including
5. Expensive tables, columns, relationship and data types
6. High Impact of failure
Importance
Types of Databases - Data Organization: Organize data into
1. Relational Databases - table (rows and well-defined tables with relevant attributes.
columns) - Relationships: Show how tables are related
- -proposed by E.F. Codd in 1970 and depict data types for columns.
- MySQL, PostgreSQL, Oracle, - Maintenance: Facilitate maintaining clean
Microsoft SQL Server, Microsoft data related to an application.
Access, SQLite
 - Avoid Reverse-Engineering: Prevent the
need for reverse-engineering the data
model. Normalization
- Efficient Queries: Enable efficient data - Normalization simplifies basic database
retrieval for reporting and analytics. tasks and resolves insert, delete, and
- Cost Reduction: Reduce the need for update anomalies.
extensive reverse-engineering, saving time
and costs 1. 1NF/ data atomicity
- Data atomicity means having only one
Relationship Types single instance value of a column attribute
1. One to One in any table field.
2. One to Many - Tables should contain only one value per
3. Many to Many field to avoid redundancy and inconsistency
- Achieve data atomicity and eliminate
Data Integrity repeating groups of data.
- Key Integrity - 1NF
- Referential Integrity
- Constraints ensure data integrity

Constraints
- Domain Constraints - rules for the
valid values that can be stored in a - Data atomicity
specific column
- Primary key is used to identify a
table field that contains unique
values.
- Foreign keys link data in one table
to data in another table, creating
relationships.
- Unique Key 2. 2NF/
- Not Null - functional dependency - One
column's unique values determine
Entities - are objects with defining properties in a the values of another column.
database. - the relationship between two
attributes in a table.
1. Simple Attributes: Cannot be classified - partial dependency
further (e.g., grade). - Occurs when a table has a
2. Single-Valued Attributes: Store one value composite primary key
per entity (e.g., date of birth). (composed of two or more
3. Composite Attributes: Can be split into columns).
sub-components (e.g., name -> first and last - All non-key attributes must
name). depend on the entire primary
4. Multi-Valued Attributes: Store multiple key, not just part of it.
values (should be avoided).
5. Derived Attributes: Values are derived 3. 3NF
from other attributes (e.g., age from date of - To achieve 3NF, a database must
birth). first be in 1NF and 2NF.
6. Key Attributes: Hold unique values to - transitive dependency
identify entities (e.g., student ID).
 - occurs when one non-key security of a database or for granting or
attribute depends on another revoking a data operation to the user
non-key attribute. 4. TCL - Transaction Control Language - for
managing transactions within relational
DBMS.

SQL - Structured Query Language

- The standard language used to interact to
database
- Language for storing, manipulating and
retrieving data in database

SQL Subcomponents:
1. DDL - Data Definition Language - we are
done with the structure of the database with
the use of
- CREATE DATABASE/ TABLE
- DROP DATABASE/ TABLE
- ALTER DATABASE/ TABLE
2. DML - Data Manipulation Language
- C REATE - INSERT INTO Statement
- R EAD - SELECT Statement
- U PDATE - UPDATE Statement
- D ELETE - DELETE FROM
Statement
3. DCL - Data Control Language - deals with
the permissions, access control, and