LECTURE 2

ADVANTAGES OF DATABASE
MANAGEMENT SYSTEM
 Reducing Data Redundancy
The file based data management systems contained multiple files that were stored in
many different locations in a system or even across multiple systems. Because of this,
there were sometimes multiple copies of the same file which lead to data redundancy.
This is prevented in a database as there is a single database and any change in it is
reflected immediately. Because of this, there is no chance of encountering duplicate
data.

 Sharing of Data
In a database, the users of the database can share the data among themselves. There are
various levels of authorisation to access the data, and consequently the data can only
be shared based on the correct authorisation protocols being followed.
Many remote users can also access the database simultaneously and share the data
between themselves.
Data Integrity
Data integrity means that the data is accurate and consistent in the
database. Data Integrity is very important as there are multiple
databases in a DBMS. All of these databases contain data that is
visible to multiple users. So it is necessary to ensure that the data
is correct and consistent in all the databases and for all the users.

 Data Consistency
Data consistency is ensured in a database because there is no data
redundancy. All data appears consistently across the database and
the data is same for all the users viewing the database. Moreover,
any changes made to the database are immediately reflected to all
the users and there is no data inconsistency.
 Enforcement of integrity constraints
Database management systems must provide the ability to define
and enforce certain constraints to ensure that users enter valid
information and maintain data integrity. A database constraint is
a restriction or rule that dictates what can be entered or edited in
a table such as a postal code using a certain format or adding a
valid city in the City field.
There are many types of database constraints. Data type, for
example, determines the sort of data permitted in a field, for
example numbers only. Data uniqueness such as the primary
key ensures that no duplicates are entered. Constraints can be
simple (field based) or complex (programming).
 Restriction of unauthorized access
Not all users of a database system will have the same accessing
privileges. For example, one user might have read-only
access (i.e., the ability to read a file but not make changes), while
another might have read and write privileges, which is the ability
to both read and modify a file. For this reason, a database
management system should provide a security subsystem to
create and control different types of user accounts and restrict
unauthorized access.
 Data independence

Another advantage of a database management system is how it

allows for data independence. In other words, the system data
descriptions or data describing data (metadata) are separated
from the application programs. This is possible because changes
to the data structure are handled by the database management
system and are not embedded in the program itself.
 Data Security
Data Security is vital concept in a database. Only authorised users should be allowed to
access the database and their identity should be authenticated using a username and
password. Unauthorised users should not be allowed to access the database under any
circumstances as it violates the integrity constraints.
 Privacy

The privacy rule in a database means only the authorized users can access a database
according to its privacy constraints. There are levels of database access and a user can
only view the data he is allowed to. For example - In social networking sites, access
constraints are different for different accounts a user may want to access.
 Backup and Recovery

Database Management System automatically takes care of backup and recovery. The users
don't need to backup data periodically because this is taken care of by the DBMS.
Moreover, it also restores the database after a crash or system failure to its previous
condition.
CHARACTERISTIC OF DATABASE
APPROACH
 Self Describing Nature of Database
Database system contains not only the database but also
the complete definition and description of database
structure and constraints .

 Support of Multiple use of data

Database has many uses, each of may required different
perspectives or view of the database.

o Sharing of Data and Multiuser Transaction Processing

CONTD..
 Insulation between program and data
In the file-based system, the structure of the data files is
defined in the application programs so if a user wants to
change the structure of a file, all the programs that
access that file might need to be changed as well.
On the other hand, in the database approach, the data
structure is stored in the system catalogue and not in the
programs. Therefore, one change is all that is needed to
change the structure of a file. This insulation between the
programs and data is also called program-data
independence
DATABASE USERS
 End users are the people whose job requires access to
the Database for querying , updating , generating
reports .
 Types of Uses

1 – NAIVE USERS – Their main job functions revolves

around constantly querying and updating the Database,
using standard types of queries called Canned
Transactions . Example – ATM machines and reservation
clerks
2 – SOPHISTICATED USERS – These include engineers ,
scientists , business analyst and others who thoroughly
familiarize themselves with facilities of Database in
order to implement their applications to meet requirments.

3 – SPECIALIZED USERS – These are sophisticated users

who write specialized Database applications that do not fit
into traditional data process.

4- APPICATION PROGRAMMERS – These are

computer professionals who write application
programmes .
THREE SCHEMA ARCHITECTURE
 This framework is used to describe the structure of a specific
database system.
 The three schema architecture is also used to separate the user
applications and physical database.

In the above diagram:

 It shows the DBMS architecture.

 Mapping is used to transform the request and response between

various database levels of architecture.
 Mapping is not good for small DBMS because it takes more
time.
 In External / Conceptual mapping, it is necessary to transform
the request from external level to conceptual schema.
 In Conceptual / Internal mapping, DBMS transform the request
from the conceptual to internal level.
INTERNAL LEVEL

 The internal level has an internal schema which describes the

physical storage structure of the database.
 The internal schema is also known as a physical schema.

 It uses the physical data model. It is used to define that how

the data will be stored in a block.
 The physical level is used to describe complex low-level data
structures in detail.
CONCEPTUAL LEVEL
Conceptual Level
 The conceptual schema describes the design of a database at the
conceptual level. Conceptual level is also known as logical level.
 The conceptual schema describes the structure of the whole
database.
 The conceptual level describes what data are to be stored in the
database and also describes what relationship exists among those
data.
 In the conceptual level, internal details such as an
implementation of the data structure are hidden.
 Programmers and database administrators work at this level.
EXTERNAL/VIEW LEVEL
 At the external level, a database contains several schemas that
sometimes called as subschema. The subschema is used to
describe the different view of the database.
 An external schema is also known as view schema.

 Each view schema describes the database part that a particular

user group is interested and hides the remaining database from
that user group.
 The view schema describes the end user interaction with
database systems.
DATA INDEPENDENCE
 Data independence can be explained using the three-schema
architecture.

 Data independence refers characteristic of being able to

modify the schema at one level of the database system
without altering the schema at the next higher level.
TYPES OF DATA INDEPENDENCE
LOGICAL DATA INDEPENDENCE

 Logical data independence refers characteristic of being

able to change the conceptual schema without having to
change the external schema.
 Logical data independence is used to separate the
external level from the conceptual view.
 If we do any changes in the conceptual view of the data,
then the user view of the data would not be affected.
 Logical data independence occurs at the user interface
level.
PHYSICAL DATA INDEPENDENCE

 Physical data independence can be defined as the

capacity to change the internal schema without having to
change the conceptual schema.
 If we do any changes in the storage size of the database
system server, then the Conceptual structure of the
database will not be affected.
 Physical data independence is used to separate
conceptual levels from the internal levels.
 Physical data independence occurs at the logical
interface level.
THANK YOU