NAME : MUSA LUCKY

REG NO : IN13/00045/24

UNIT : COMP 204

TASK : ASSIGNMENT

QUESTION : DISCUSS HOW DATABASE SYSTEMS HAVE EVOLVED OVER TIME UP TO

In the early days of computing, data storage and management were done in a relatively simple way:
through file systems. These file systems were primitive and lacked any real structure, meaning they
were inefficient and difficult to manage as data grew in volume and complexity. Most of the data was
stored in flat files—essentially, just large blocks of text or numbers with no way to meaningfully
organize or relate them to one another.

In the first-generation systems, files were stored in basic formats with no advanced features for
handling data relationships. These systems lacked indexing, which made retrieving specific data a
slow and inefficient process. In essence, they were little more than large digital filing cabinets, with
no real structure to help users find what they needed quickly.

As data storage needs grew, file systems became increasingly inadequate. The sheer volume of data
began to overwhelm the capacity of flat files, and organizations needed a more efficient way to store
and access their information. This led to the development of the second-generation file systems—
systems that were more sophisticated and integrated with the operating system (OS).

OS-managed file systems allowed for the basic management of data storage, but still had limitations
in terms of how the data could be related or queried. These file systems offered some degree of
organization, but the data was still stored in a way that made it difficult to manipulate or retrieve
efficiently. While this marked an improvement over the first-generation file systems, it was still far
from ideal.

In response to the limitations of early file systems, the next major leap in the evolution of database
systems came with the development of Database Management Systems (DBMS). A DBMS is a
software system designed to store, manage, and facilitate access to data in a structured way. Unlike
early file systems, DBMS introduced the concept of a centralized repository where data could be
stored in a highly organized and structured manner.

One of the key innovations that DBMS introduced was the concept of data independence. Data
independence refers to the ability to change the structure of the database without affecting the way
users interact with it. This concept is broken down into two primary types of data independence:

 Physical data independence: This refers to the ability to change the physical storage of the
data (e.g., moving it from one disk to another or changing the file format) without affecting
the logical structure of the database or the applications that interact with it.

 Logical data independence: This refers to the ability to change the logical structure of the data
(e.g., adding new tables or relationships) without requiring changes to the application code
that interacts with the database.

The first database management systems (DBMS) were created to handle complex data for businesses
in the 1960s. These systems included Charles Bachman's Integrated Data Store (IDS) and IBM's
Information Management System (IMS). Databases were first organized into tree-like structures using
hierarchical and network models.

Edgar F. Codd popularized the relational model in the 1970s, transforming database management
systems (DBMS) with the concept of arranging data in tables, or relations and utilizing SQL for
queries. As a result, contemporary DBMS systems like Oracle and MySQL were established. These
systems are still developing today, incorporating newer technologies like NoSQL databases to handle
unstructured data.

Evolution of Data Storage and Processing Techniques

 1950s and early 1960s: Magnetic tapes were developed for data storage. Data processing
tasks such as payroll were automated, with data stored on tapes. Processing of data consisted
of reading data from one or more tapes and writing data to a new tape. Data could also be
input from punched card decks, and output to printers.

 Late 1960s and 1970s: Widespread use of hard disks in the late 1960s changed the scenario
for data processing greatly, since hard disks allowed direct access to data. The position of data
on disk was immaterial, since any location on disk could be accessed in just tens of
milliseconds. With disks, network and hierarchical databases could be created that allowed
data structures such as lists and trees to be stored on disk. Programmers could construct and
manipulate these data structures. A landmark paper by Codd [1970] defined the relational
model and nonprocedural ways of querying data in the relational model, and relational
databases were born.
 1980s: Although academically interesting, the relational model was not used in practice
initially, because of its perceived performance disadvantages; relational databases could not
match the performance of existing network and hierarchical databases. That changed with
System R, a groundbreaking project at IBM Research that developed techniques for the
construction of an efficient relational database system. Excellent overviews of System R are
provided by Astrahan et al. [1976] and Chamberlin et al. [1981]. The fully functional System
R prototype led to IBM’s first relational database product, SQL/DS. At the same time, the
Ingres system was being developed at the University of California at Berkeley. It led to a
commercial product of the same name. Initial commercial relational database systems, such as
IBM DB2, Oracle, Ingres, and DEC Rdb, played a major role in advancing techniques for
efficient processing of declarative queries. By the early 1980s, relational databases had
become competitive with network and hierarchical database systems even in the area of
performance. Relational databases were so easy to use that they eventually replaced network
and hierarchical databases; programmers using such databases were forced to deal with many
low-level implementation details, and had to code their queries in a procedural fashion. Most
importantly, they had to keep efficiency in mind when designing their programs, which
involved a lot of effort. In contrast, in a relational database, almost all these low-level tasks
are carried out automatically by the database, leaving the programmer free to work at a
logical level.
 Early 1990s: The SQL language was designed primarily for decision support applications,
which are query-intensive, yet the mainstay of databases in the 1980s was transaction-
processing applications, which are update-intensive. Decision support and querying re-
emerged as a major application area for databases. Tools for analyzing large amounts of data
 saw large growths in usage. Many database vendors introduced parallel database products in
this period. Database vendors also began to add object-relational support to their databases.
 1990s: The major event of the 1990s was the explosive growth of the World Wide Web.
Databases were deployed much more extensively than ever before. Database systems now had
to support very high transaction-processing rates, as well as very high reliability and 24 × 7
availability (availability 24 hours a day, 7 days a week, meaning no downtime for scheduled
maintenance activities). Database systems also had to support Web interfaces to data.
 2000s: The first half of the 2000s saw the emerging of XML and the associated query
language XQuery as a new database technology. Although XML is widely used for data
exchange, as well as for storing certain complex data types, relational databases still form the
core of a vast majority of large-scale database applications. In this time period we have also
witnessed the growth in “autonomic-computing/auto-admin” techniques for minimizing
system administration effort. This period also saw a significant growth in use of open-source
database systems, particularly PostgreSQL and MySQL. The latter part of the decade has seen
growth in specialized databases for data analysis, in particular column-stores, which in effect
store each column of a table as a separate array, and highly parallel database systems designed
for analysis of very large data sets. Several novel distributed data-storage systems have been
built to handle the data management requirements of very large Web sites such as Amazon,
Facebook, Google, Microsoft and Yahoo!, and some of these are now offered as Web services
that can be used by application developers.