Answer

1. Describe fundamentals of Database Management Systems

 Evolution of Database Management Systems

In ancient times before the advent of computer, data started to be held in large storage items called books. And in
the end when technology advanced and knowledge increased vastly whole communities of books migrated into
what was potentially a very early form of “database” libraries. The primary goal of the database is to have data in
one way or another harvested. It is a structured collection of data(Records). The information in a database is
generally stored in tables with data that may or may not be interconnected. So in this case, the database contains
essentially a large number of database files and every database file is by more than a collection of records.

1.Flat files (1950s – 1960s)

Flat File Database is a sort of database that stores information in a single file or table. Records are kept on a file,
where each line is one record containing fields that can be of a fixed length or separated by comas, whitespaces,
tabs or any other character. There is no structural relationship between the record in a flat file database and it also
cannot include multiple table like as well.

Flat file database is implemented in:

Berkeley DB
SQLite
Mimesis
TheIntegrationEngineer etc.

2. Hierarchical Databases (1960s - 1970s)

Hierarchical DBMSs[edit] The first generation of database management systems were hierarchical databases, which
were also called a data structure. IBM's Information Management System (IMS) was a seminal software system that
utilized a model hardware layout to manage large volumes of information for large organizations. Hierarchical
databases organize data into a tree-like structure where each record contains one or more fields, and two types of
records: — Parent Records : Each parent may be associated with multiple child records. It made more sense in
certain kinds of applications, but it could be inflexible for any kind of complex queries, considering each parent can
have multiple children while a child itself could only have one unique parent i.

3. Network Databases (1960s - 1970s)

Network databases: and the Network Database Model (similar to CODASYL), used a more general structure by
allowing many-to-many relationships between records, thus enabling a structurally more complex database. Simple
Tables are for when records in the data do not relate to one another (you could combine your transactions with
SKU information, but we would still call it a Simple Table) Relationships use a graph like structure where a record
can have multiple parent or child records This worked for many-to-many cases, but was quite cumbersome.
Network database is implemented in:

Digital Equipment Corporation DBMS-10

4. Relational Databases (1970s - 1980s)

Database management was transformed by the relational model proposed by Edgar F. Codd in 1970. A relational
database is a type of database that uses a structure similarity to how data is stored in tables and relationships, this
must include an SQL interface for managing the system. Data management and querying was much easier in this
model, so it became the dominant DBMS paradigm. Examples of relational databases are IBM DB2, Oracle
Database and Microsoft SQL Server.

Implementation of Relational Database:

Oracle
Microsoft
IBM
My SQL
PostgreSQL
SQLite

5. Object-Oriented Databases (1980s - 1990s)

Object oriented databases were introduced to correspond with object oriented programming languages and
database systems. Namely, they represent data as objects a la object-oriented programming. The collection did
provide benefits for selected applications with complex data relationships or multimedia, but did not have the
same degree of adoption as relational-databases.

6. NoSQL Databases (2000s - Present)

NoSQL databases were born in order to solve the problems of non-relational struggles, trying to tackle horizontal
scaling and non-structured data. Types of NoSQL Databases: NUO-SQL databases are broadly classified into 4 types
Wiz Document stores (MongoDB) Wiz Key-value stores (Redis) Wiz Column-family stores (Cassandra) Wiz Graph
databases (Neo4j). Bigtable is optimized for large-scale workloads with a high volume of data and provides a
schema design that can evolve.

7. Cloud Databases and Data Warehousing (2010s - Present)

A cloud database is a database built to run in a public cloud environment to help organize, store, and manage data
within an organization.

Advantages and Disadvantages of the Database Management Systems

approach vs. File Based Systems approach

Oversee development and maintenance standards. Helps reduce redundancy.

Bypass file management inconsistencies Maintain data isolation integrity Strong theoretical underpinnings (for
relational model).

Sometimes faster and cheaper than a DBMS

Homogenized data management practice.

Application programmers do not need to know how data is represented and stored.

DBMS has many sophisticated functionalities to store and access the information effectively. Gives data integrity &
Security.

Disadvantages of File System

The data file for each app is its own, so if you need to keep that same data you would have to log and save it more
than once.

It is able to manage millions of items even for big corporations. A lot of work was required.

It can hold records for big corporations using lots of items.

In file handling systems, it works at a different level of data dependencies which are different because the problem
in file handling is that there may be lack in compatibility to work with other formats(we will see this). Time-
consuming.
Limited Data Sharing.
Security issue.

Advantages of DBMS
Situations where data’s integrity and security are being provided.

Standardized data collection.

Data representation and storage is hidden from application programmers.

A database management system processes many features to save and extract data powerfully.

DBMS enforces the integrity constraints to remain secure at all costs and which are not allowed unauthorizedness
access of object data.

Less time to develop applications

Provides data independence.

Disadvantages of DBMS

Many database management systems take months to implement as complex, and require user training time before
one can start using the DBMS.
Numerous users attempting to use a program at the same time can result in data being lost.
Databases are expensive to purchase, difficult and costly to operate.
DBMSs are not able to do complex calculations.
Otherwise we will end up with bigger datasets, to have more predictable query response times.
A fast SoC for data processing is needed.
One of the major side-effect is power failure (that in return can make the database to crash, or can bring down
entire system)

2. Describe the following job roles related to Database Management Systems.

Data Administrator (DA):

Role: A Data Administrator deals with overseeing data. They define data policies, standards and operating
procedures to adhere to and ensure that data quality, security, and regulatory compliance are maintained. In these
jobs, they tend to work on data access control and system integration strategies that might get overlooked or the
team is not painting excessively close attention towards this aspect of data lifecycle management.

Database Administrator (DBA):

Role:A Database Administrator manages and maintains database systems. They are responsible for database
performance, security, backups and recovery. DBAS handle tasks such as installing and configuring database
software, monitoring performance and ensuring that the database runs smoothly and efficiently.
Database Designer:

Role: A Database Designer is involved in designing the database schema. This role focuses on creating the structure
of the database, including tables, relationships, indexes and constraints. The goal is to design a database that meets
the needs of the application while ensuring data efficiency.

Application Developer:

Role: An Application Developer is responsible to write and maintain software applications that interact with the
database. They write the application logic or implement it, which means, they write queries and manage
transactions with data and interact the application with database. They worry about the application and how well it
uses data in their database.

End User:

Role: An End User is the person who interacts with the application or system to retrieve or input data. End Users
use applications to perform their tasks such as generating reports, querying data or updating records. They are not
involved in the technical aspects of database management but rely on the database and applications for their daily
operations.