Unit 1 :- Introduction To Data Base Management System

DBMS Architecture
o The DBMS design depends upon its architecture. The basic client/server architecture is used to
deal with a large number of PCs, web servers, database servers and other components that are
connected with networks.
o The client/server architecture consists of many PCs and a workstation which are connected via
the network.
o DBMS architecture depends upon how users are connected to the database to get their request
done.

Types of DBMS Architecture

Database architecture can be seen as a single tier or multi-tier. But logically, database
architecture is of two types like: 2-tier architecture and 3-tier architecture.

1-Tier Architecture
o In this architecture, the database is directly available to the user. It means the user can directly sit
on the DBMS and uses it.
o Any changes done here will directly be done on the database itself. It doesn't provide a handy tool
for end users.
o The 1-Tier architecture is used for development of the local application, where programmers can
directly communicate with the database for the quick response.

Notes By :- Dr. J.R. Mahajan 1

Unit 1 :- Introduction To Data Base Management System

2-Tier Architecture
o The 2-Tier architecture is same as basic client-server. In the two-tier architecture, applications on
the client end can directly communicate with the database at the server side. For this interaction,
API's like: ODBC, JDBC are used.
o The user interfaces and application programs are run on the client-side.
o The server side is responsible to provide the functionalities like: query processing and transaction
management.
o To communicate with the DBMS, client-side application establishes a connection with the server
side.

Fig: 2-tier Architecture

3-Tier Architecture
o The 3-Tier architecture contains another layer between the client and server. In this architecture,
client can't directly communicate with the server.
o The application on the client-end interacts with an application server which further communicates
with the database system.
o End user has no idea about the existence of the database beyond the application server. The
database also has no idea about any other user beyond the application.
o The 3-Tier architecture is used in case of large web application.

Notes By :- Dr. J.R. Mahajan 2

Unit 1 :- Introduction To Data Base Management System

Fig: 3-tier Architecture

Data Abstraction
It is a process of hiding unwanted or irrelevant details from the end user. It provides a different
view and helps in achieving data independence which is used to enhance the security of data.
The database systems consist of complicated data structures and relations. For users to access
the data easily, these complications are kept hidden, and only the relevant part of the database is
made accessible to the users through data abstraction.
Levels of abstraction for DBMS
Database systems include complex data-structures. In terms of retrieval of data, reduce
complexity in terms of usability of users and in order to make the system efficient, developers
use levels of abstraction that hide irrelevant details from the users. Levels of abstraction simplify
database design.
Mainly there are three levels of abstraction for DBMS, which are as follows −

 Physical or Internal Level

 Logical or Conceptual Level
 View or External Level
These levels are shown in the diagram below –

Notes By :- Dr. J.R. Mahajan 3

Unit 1 :- Introduction To Data Base Management System

Physical or Internal Level

It is the lowest level of abstraction for DBMS which defines how the data is actually stored, it
defines data-structures to store data and access methods used by the database. Actually, it is
decided by developers or database application programmers how to store the data in the
database.
So, overall, the entire database is described in this level that is physical or internal level. It is a
very complex level to understand. For example, customer's information is stored in tables and
data is stored in the form of blocks of storage such as bytes, gigabytes etc.
Logical or Conceptual Level
Logical level is the intermediate level or next higher level. It describes what data is stored in the
database and what relationship exists among those data. It tries to describe the entire or whole
data because it describes what tables to be created and what are the links among those tables that
are created.
It is less complex than the physical level. Logical level is used by developers or database
administrators (DBA). So, overall, the logical level contains tables (fields and attributes) and
relationships among table attributes.
View or External Level
It is the highest level. In view level, there are different levels of views and every view only
defines a part of the entire data. It also simplifies interaction with the user and it provides many
views or multiple views of the same database.
View level can be used by all users (all levels' users). This level is the least complex and easy to
understand.
For example, a user can interact with a system using GUI that is view level and can enter details
at GUI or screen and the user does not know how data is stored and what data is stored, this
detail is hidden from the user.

Notes By :- Dr. J.R. Mahajan 4

Unit 1 :- Introduction To Data Base Management System

Data Independence
Data independence is the ability to modify the scheme without affecting the programs and the
application to be rewritten. Data is separated from the programs, so that the changes made to the
data will not affect the program execution and the application.
We know the main purpose of the three levels of data abstraction is to achieve data
independence. If the database changes and expands over time, it is very important that the
changes in one level should not affect the data at other levels of the database. This would save
time and cost required when changing the database.
There are two levels of data independence based on three levels of abstraction. These are as
follows −
 Physical Data Independence
 Logical Data Independence

Physical Data Independence

Physical Data Independence means changing the physical level without affecting the logical
level or conceptual level. Using this property, we can change the storage device of the database
without affecting the logical schema.
The changes in the physical level may include changes using the following −
 A new storage device like magnetic tape, hard disk, etc.
 A new data structure for storage.
 A different data access method or using an alternative files organization technique.
 Changing the location of the database.

Logical Data Independence

Logical view of data is the user view of the data. It presents data in the form that can be
accessed by the end users.
Codd’s Rule of Logical Data Independence says that users should be able to manipulate the
Logical View of data without any information of its physical storage. Software or the computer
program is used to manipulate the logical view of the data.
Database administrator is the one who decides what information is to be kept in the database and
how to use the logical level of abstraction. It provides the global view of Data. It also describes
what data is to be stored in the database along with the relationship.
The data independence provides the database in simple structure. It is based on application
domain entities to provide the functional requirement. It provides abstraction of system
functional requirements. Static structure for the logical view is defined in the class object
diagrams. Users cannot manipulate the logical structure of the database.
The changes in the logical level may include −
Notes By :- Dr. J.R. Mahajan 5
Unit 1 :- Introduction To Data Base Management System

 Change the data definition.

 Adding, deleting, or updating any new attribute, entity or relationship in the database.

RDBMS (relational database management system)

A relational database management system (RDBMS) is a collection of programs and capabilities

that enable IT teams and others to create, update, administer and otherwise interact with
a relational database. RDBMSes store data in the form of tables, with most commercial relational
database management systems using Structured Query Language (SQL) to access the database.
However, since SQL was invented after the initial development of the relational model, it is not
necessary for RDBMS use.

The RDBMS is the most popular database system among organizations across the world. It
provides a dependable method of storing and retrieving large amounts of data while offering a
combination of system performance and ease of implementation.

RDBMS vs. DBMS

In general, databases store sets of data that can be queried for use in other applications. A
database management system supports the development, administration and use of database
platforms.

An RDBMS is a type of database management system (DBMS) that stores data in a row-based
table structure which connects related data elements. An RDBMS includes functions that
maintain the security, accuracy, integrity and consistency of the data. This is different than the
file storage used in a DBMS.

Other differences between database management systems and relational database management
systems include:

 Number of allowed users. While a DBMS can only accept one user at a time, an
RDBMS can operate with multiple users.

Notes By :- Dr. J.R. Mahajan 6

Unit 1 :- Introduction To Data Base Management System

 Hardware and software requirements. A DBMS needs less software and hardware
than an RDBMS.

 Amount of data. RDBMSes can handle any amount of data, from small to large, while a
DBMS can only manage small amounts.

 Database structure. In a DBMS, data is kept in a hierarchical form, whereas an RDBMS

utilizes a table where the headers are used as column names and the rows contain the
corresponding values.

 ACID implementation. DBMSes do not use the atomicity, consistency, isolation and
durability (ACID) model for storing data. On the other hand, RDBMSes base the structure of
their data on the ACID model to ensure consistency.

 Distributed databases. While an RDBMS offers complete support for distributed

databases, a DBMS will not provide support.

 Types of programs managed. While an RDBMS helps manage the relationships

between its incorporated tables of data, a DBMS focuses on maintaining databases that are
present within the computer network and system hard disks.

 Support of database normalization. An RDBMS can be normalized, but a DBMS

cannot.

Database Schema
A database schema is the skeleton structure that represents the logical view of the entire
database. It defines how the data is organized and how the relations among them are associated.
It formulates all the constraints that are to be applied on the data.
A database schema defines its entities and the relationship among them. It contains a descriptive
detail of the database, which can be depicted by means of schema diagrams. It’s the database
designers who design the schema to help programmers understand the database and make it
useful.

Notes By :- Dr. J.R. Mahajan 7

Unit 1 :- Introduction To Data Base Management System

A database schema can be divided broadly into two categories −

 Physical Database Schema − This schema pertains to the actual storage of data and its
form of storage like files, indices, etc. It defines how the data will be stored in a
secondary storage.
 Logical Database Schema − This schema defines all the logical constraints that need to
be applied on the data stored. It defines tables, views, and integrity constraints.

Database Instance
It is important that we distinguish these two terms individually. Database schema is the skeleton
of database. It is designed when the database doesn't exist at all. Once the database is
operational, it is very difficult to make any changes to it. A database schema does not contain
any data or information.
A database instance is a state of operational database with data at any given time. It contains a
snapshot of the database. Database instances tend to change with time. A DBMS ensures that its
every instance (state) is in a valid state, by diligently following all the validations, constraints,
and conditions that the database designers have imposed.

Data models
Data models define how the logical structure of a database is modeled. Data Models are
fundamental entities to introduce abstraction in a DBMS. Data models define how data is
connected to each other and how they are processed and stored inside the system.
The very first data model could be flat data-models, where all the data used are to be kept in the
same plane. Earlier data models were not so scientific, hence they were prone to introduce lots of
duplication and update anomalies.

Entity-Relationship Model

Notes By :- Dr. J.R. Mahajan 8

Unit 1 :- Introduction To Data Base Management System

Entity-Relationship (ER) Model is based on the notion of real-world entities and relationships
among them. While formulating real-world scenario into the database model, the ER Model
creates entity set, relationship set, general attributes and constraints.
ER Model is best used for the conceptual design of a database.
ER Model is based on −
 Entities and their attributes.
 Relationships among entities.
These concepts are explained below.

 Entity − An entity in an ER Model is a real-world entity having properties

called attributes. Every attribute is defined by its set of values called domain. For
example, in a school database, a student is considered as an entity. Student has various
attributes like name, age, class, etc.
 Relationship − The logical association among entities is called relationship.
Relationships are mapped with entities in various ways. Mapping cardinalities define the
number of association between two entities.
Mapping cardinalities −
o one to one
o one to many
o many to one
o many to many

Relational Model
The most popular data model in DBMS is the Relational Model. It is more scientific a model
than others. This model is based on first-order predicate logic and defines a table as an n-ary
relation.

Notes By :- Dr. J.R. Mahajan 9

Unit 1 :- Introduction To Data Base Management System

The main highlights of this model are −

 Data is stored in tables called relations.

 Relations can be normalized.
 In normalized relations, values saved are atomic values.
 Each row in a relation contains a unique value.
 Each column in a relation contains values from a same domain.

Notes By :- Dr. J.R. Mahajan 10