Course : 20CS401- Database Management System

Module : Data Modeling and Relational Query Language

Topic : Introduction to DBMS

Faculty : Sajeev Ram. A

Purpose Of Database System

Example: Student database in university

Disadvantages of File Processing System

• Data redundancy and inconsistency (Different programs/Languages)

• Difficulty in Accessing Data (Student with particular postal code)

• Data isolation (data in various files)

• Integrity problems (accounts issue- btwn dept)

• Atomicity problems (failure during amt trnsc)

• Concurrent-access anomalies (budget updating)

• Security Problem (Access Rights)

File System Vs DB
Evolution of DBMS
• 1950-60
• Magnetic tapes

• 1960-70
• Hard Disks

• Network and hierarchical DB’s

• Late 1970  Relational model

• 1980
• Parallel and Distributed Dabatbases

• 1990
• Early 1990  SQL

• Late World Wide Web (24*7)

Evolution of DBMS . . .

• File Management System

• Hierarchical database System

• Network Database System

• Relational Database System

Users of DBMS
Naive users
• Naive users are unsophisticated users who interact with the system by invoking one of the
application programs that have been written previously.

Application programmers
• Application programmers are computer professionals who write application programs.

Sophisticated users:
• form their requests in a database query language. They submit each such query to a query
processor

Specialized users:
• Specialized users are sophisticated users who write specialized database applications
Database Administrator (DB ADMIN)

• Central control of both the data and the programs that access those data

• Roles/Responsibilities
• Schema definition

• Schema and physical-organization modification

• Granting of authorization for data access

• Routine maintenance
 Video Lecture

Learn What is Database | Types of Database | DBMS

Database System Architecture
Database System Architecture
Data Abstraction
• Major purpose of a database system is to provide users
with an abstract view of the data. The system hides certain
details of how the data are stored and maintained.

• Developers hide the complexity from users through

several levels of abstraction
 Physical level (How stored)

 Logical level (what Data? What Relationship?)

 View level (Part of the entire database)

Data Abstraction . . .
• Instances & Schemas

• The collection of information stored in the database at a particular moment is called an instance of the

database.

• Overall design of the database is called the database schema.

• Physical Schema (internal level)

• describes the physical storage structure of the database. The internal schema uses a physical data model and

describes the complete

• Logical Schema (conceptual level)

• describes the structure of the whole database for a community of users

• Subschemas (External or View level)

• external schema describes the part of the database that a particular user group is interested in and hides the rest

of the database from that user group.

Data Independence

Property of DBMS that helps you to change the Database schema at one level of a
database system without requiring to change the schema at the next higher level.

Two types of data independence

• Physical data independence
• Logical data independence
Data Independence - Physical Data Independence

• Physical data independence helps you to separate conceptual levels from the internal/physical levels
• With Physical independence, you can easily change the physical storage structures or devices with
an effect on the conceptual schema.
• Any change done would be absorbed by the mapping between the conceptual and internal levels

Examples
• Using a new storage device like Hard Drive or Magnetic Tapes

• Modifying the file organization technique in the Database

• Switching to different data structures.

• Changing the access method.

• Modifying indexes.

• Changes to compression techniques or hashing algorithms.

• Change of Location of Database from say C drive to D Drive

Data Independence - Logical Data Independence

• Logical Data Independence is the ability to change the conceptual scheme without changing
External views & External API or programs
• Any change made will be absorbed by the mapping between external and conceptual levels.
• When compared to Physical Data independence, it is challenging to achieve logical data
independence.
Examples
• Add/Modify/Delete a new attribute, entity or relationship is possible without a rewrite of existing application
programs

• Merging two records into one

• Breaking an existing record into two or more records

Data Independence
Physical Vs Logical Data Independence

Logica Data Independence Physical Data Independence

Logical Data Independence is mainly concerned with Mainly concerned with the storage of the data.
the structure or changing the data definition.

It is difficult as the retrieving of data is mainly It is easy to retrieve.

dependent on the logical structure of data.

Compared to Logic Physical independence it is Compared to Logical Independence it is easy to

difficult to achieve logical data independence. achieve physical data independence.

You need to make changes in the Application program A change in the physical level usually does not need
if new fields are added or deleted from the database. change at the Application program level.

Modification at the logical levels is significant Modifications made at the internal levels may or may
whenever the logical structures of the database are not be needed to improve the performance of the
changed. structure.

Concerned with conceptual schema Concerned with internal schema

Example: Add/Modify/Delete a new attribute Example: change in compression techniques, hashing

algorithms, storage devices, etc
Data Independence - Importance
 Helps you to improve the quality of the data

 Database system maintenance becomes affordable

 Enforcement of standards and improvement in database security

 You don't need to alter data structure in application programs

 Permit developers to focus on the general structure of the Database rather than worrying about
the internal implementation

 It allows you to improve state which is undamaged or undivided

 Database incongruity is vastly reduced.

 Easily make modifications in the physical level is needed to improve the performance of the
system.
 Video Lecture

System Design: What is 3 tier

DBMS Architecture
architecture?
 Video Lecture

Introduction to Database Management Systems 1:

Fundamental Concepts

Prof. Dr. Bart Baesens

professor of Big Data & Analytics at KU Leuven (Belgium)
lecturer at the University of Southampton (United Kingdom)
https://www.bartbaesens.com/