A.

Managing Data
B. A Historical Perspective
C. File Systems Versus a DBMS
D. Queries in a DBMS
E. Transaction Management
F. Structure of a DBMS
G. People Who Work with DBMS

MANAGING DATA
Database is a means of managing data,
DBMS means a system that manages data from a database.
Data – unprocessed facts
Information – processed data
Database – collection of related data
Metadata – data about data

FILE SYSTEMS
File system logs every record, and then assigns an index so that when the file is being
retrieved, the user will just find or call on the index.

Distinction is only the index and data are unorganized.

DBMS
collection of interrelated data
set of programs to access those data. (using atm)
Primary goal of a dbms is to store and retrieve data, and in doing so, it should be
convenient and efficient.
Manage large bodies of information

Why do we use database instead of a file system?

In handling large sizes of data that needs to be stored, for example keeping records of
purchases from a store. (product name, date of purchase, name of the buyer, etc) In
every date, every purchases are logged. It’s manageable for a few months, but as the
time goes by and the store grows exponentially. Handling the records through file
systems is getting unmanageable and unmaintainable.
Problems:
Extensive space is needed to accommodate enormous sizes of files.
 Prone to permanent losses of records.
Recoverability of lost records is not always available.
In keeping specific records, duplicates may exist.

FILE SYSTEMS VS DBMS

Structure:

File system is the arrangement of files and data on the storage

DBMS uses a software in managing, manipulating, and maintaining data

Data Redundancy:

File systems are prone to redundant data

DBMS assures that data redundancy are avoided

Backup and Recovery:

File System doesn’t provide a backup for the data

DBMS has a feature for making sure that whatever happens, data is retrievable and
backed up.

Query Processing:

File Systems doesn’t have an efficient query system since file systems are built to just
locate where files are stored. It mainly gives the directories of the files.
DBMS provides a query system, where if queries are made in the system, it provides
what the users are requesting to do.

Consistency:

Lesser consistency for File System.

DBMS provides data normalization or the data are being cleaned regularly to remove
unstructured and redundant data

Complexity:

Admittedly, File Systems are less complicated but since DBMS assures that data is being
managed efficiently, it is more complex.
Security Constraints:

File system, grants access to anyone while DBMS provides restricted view of the data
depending on their level of clearance.

Cost:

File systems are cheaper because it doesn’t require what DBMS provides. (maintaining
the database, storage cost, ensuring that when system fails records are still occurring,
etc. DBMS is much expensive because it makes sure data is being managed accordingly.

Data Independence:

When a user changes something to the data in file systems, it is changed permanently.
But in DBMS, users can only change what they have access to. (i.e. individual accounts)
they cannot change the data stored in the physical storage.

User Access:

File Systems can only be accessed by one user at a time, DBMS provides concurrency
where multiple people can use the system at a time.

Sharing:

Data is distributed in many files, meaning that the data is spread throughout the storage
so it’s harder to share the files. You would have to know where each of the files are
stored to be able to share. But in DBMS, it has feature that data is centralized.

Data Abstraction:

Every user is privy of the information presented in the storage, but in DBMS users can
only see what they need to see.

WHEN IS IT OKAY TO USE FILE SYSTEMS OVER A DBMS:

The idea is that, you should use File Systems instead of DBMS if the requirements of
your record keeping doesn’t require heavy equipment/programs. (for example: small
business store that just needs to keep the records of their inventory and purchased
goods so they can keep track of their profit. The cost of using DBMS would not justify
the needs of the business.

TRANSACTIONS:
Transactions are defined as any activities made within the database. Queries are
transactions.

Atomicity – transaction either happens or not, no in-between.

Consistency – if a transaction was completed, it already records to the system, if the

transaction wasn’t finished before the system fail, it automatically cancels out the
transaction and rolls back to the state of the data before the transaction starts.

Isolation – individual transactions are carried out in separate environment to ensure

concurrency

Durability – ensures that the database will not fall apart.

Three Tier Architecture

In this level, you will see the GUI, Web Interface, face of the
Client/Users Database in the pov of the users. Each users, has their own specific
tool that they can use to access and manipulate data from the
database or whatever activities they may do on the database.

In this level, you will see how the queries are being processed
Application/Web through the application programs. This level handles the servers for
Server your database to be accessed remotely.

In this level, resides the database itself

Database Server

2 important component in the architecture:

Query Processor
Storage Manager
- provides the interaction between the low level data stored and application
programs (what users use to access the database)
- Handles the queries submitted to the system, received from the query processor
- Interacts with the file manager
 - Translates DML statements into low-level file system commands
- Responsible for storing, retrieving, and updating data
Buffer Manager – responsible for fetching the data from the database
Authority integrity manager
File Manager – responsible for allocation space on the disk storage
Authority & Integrity Manager - tests if the integrity constraints enforced on the
database are being satisfied (example, balance of an account should not be zero, if it
is the integrity manager aborts the transactions.) And for authority, this makes sure
that the data being accessed is with permission (for example, individual accounts on
banks, secured with pin codes, wrong information prohibits the access of the said
data)
Transaction Manager – ensures that the database remains consistent despite system
failures from hardware or software. Consequently, transaction manager makes sure
that concurrent access are carried out and does not pose any conflicts.

DML Commands – SELECT, INSERT, DELETE, UPDATE

Database are stored in the Disk Storage

Data Structures
Data Files – stores the database itself
Data Dictionary – stores the metadata
Indices – helps accessing of data item to be faster
Statistical Data – stores the statistics of the data, helps vision how to manage the
database