Search for notes by fellow students, in your own course and all over the country.

Browse our notes for titles which look like what you need, you can preview any of the notes via a sample of the contents. After you're happy these are the notes you're after simply pop them into your shopping cart.

My Basket

You have nothing in your shopping cart yet.

Title: Data Base Management System (DBMS)
Description: Introduction to Data Base Management System

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above


Introduction to Data Base Management System
(DBMS)
As the name suggests, the database management system consists of two parts
...
Database and
2
...

Data: Facts, figures, statistics etc
...
g
...

Record: Collection of related data items, e
...
in the above example the three data items had no
meaning
...

Roll
Name
Age
1
ABC
19
Table or Relation: Collection of related records
...
The rows are called
Tuples or Records
...
Consider the following collection of tables:
T1
Roll
Name
Age
1
ABC
19
2
DEF
22
3
XYZ
28
T2
Roll
Address
1
KOL
2
DEL
3
MUM
T3
Roll
Year
1
I
2
II
3
I

T4
Year
Hostel
I
H1
II
H2
We now have a collection of 4 tables
...

Because of these common attributes we may combine the data of two or more tables together to
find out the complete details of a student
...

In a database, data is organized strictly in row and column format
...
The data items within one row may belong to different data types
...
All the data items within a single attribute are
of the same data type
...
It also helps us to add, modify delete data items in the database
...

The management system is important because without the existence of some kind of rules and
regulations it is not possible to maintain the database
...
These issues must be resolved by having some kind of rules to follow in order to
maintain the integrity of the database
...

Likewise, the database that we have created already can have different aspects to reveal if seen
from different levels of abstraction
...
Generally it
means the amount of detail you want to hide
...
Let us illustrate by
a simple example
...
We do not know
what parts it is built with
...
If we open the computer case and look inside at the hard disc, motherboard, CD drive,
CPU and RAM, we are in middle level of abstraction
...

In the same manner, the database can also be viewed from different levels of abstraction to reveal
different levels of details
...
We discuss them here
...

The diagram above shows the three different schemas used in DBMS, seen from different levels
of abstraction
...
) are stored in the physical storage (Hard Disc, CD, Tape
Drive etc
...
This schema
is useful for database application developers and database administrator
...
Please note that at this level we are not interested with the raw data items
anymore, we are interested with the structure of the database
...
Conceptual
or Logical schema is very useful for database administrators whose responsibility is to maintain
the entire database
...
This is targeted for the end
users
...
We may not want the end
user to become confused with astounding amount of details by allowing him/her to have a look at

the entire database, or we may also not allow this for the purpose of security, where sensitive
information must remain hidden from unwanted persons
...
These
tables are also known as virtual tables, because they have no separate physical existence
...
Say for example, in our sample database we have
created earlier, we have a special officer whose responsibility is to keep in touch with the parents
of any under aged student living in the hostels
...
The database administrator may create a virtual table
with only these four attributes, only for the use of this officer
...
It is the property of the database which tries
to ensure that if we make any change in any level of schema of the database, the schema
immediately above it would require minimal or no need of change
...
If we
change the design of any one floor, e
...
extending the width of a room by demolishing the
western wall of that room, it is likely that the design in the above floors will have to be changed
also
...

Would not life be easy if the change could be contained in one floor only? Data independence is
the answer for this
...

Data independence can be classified into the following two types:
1
...
This is practically easier to
achieve
...

Say, you have bought an Audio CD of a recently released film and one of your friends has
bought an Audio Cassette of the same film
...
The first is digital recording on an optical media, where random access is possible
...
However, how
this change is reflected in the logical schema is very interesting
...
We have
information like Track no, Name of the Song, Name of the Artist and Duration of the Track,
things which are identical for both the CD and the Cassette
...

2
...
As we shall see, this is a little
difficult to achieve
...

Suppose the CD you have bought contains 6 songs, and some of your friends are interested in
copying some of those songs (which they like in the film) into their favorite collection
...
Each of

these collections can be compared to a view schema for that friend
...
Obviously, you will have to
ask the friends who have song 3 in their proposed collection to alter their view by deleting song 3
from their proposed collection as well
...
S/he has the flowing
functions and responsibilities regarding database management:
1
...

2
...

3
...
e
...
e
...

4
...
DBA is responsible to create user roles, which are collection of
the permissions (like read, write etc
...
S/he can
also grant additional permissions to and/or revoke existing permissions from a user if
need be
...
Defining the integrity constraints for the database to ensure that the data entered conform

to some rules, thereby increasing the reliability of data
...
Creating a security mechanism to prevent unauthorized access, accidental or intentional

handling of data that can cause security threat
...
Creating backup and recovery policy
...
It is essential to keep regular backup of the data so that
if the system fails then all data up to the point of failure will be available from a stable
storage
...


Advantages and Disadvantages of Database Management System
We must evaluate whether there is any gain in using a DBMS over a situation where we do not
use it
...

1
...
Redundancy is the problem of storing the same data item in more one place
...
Anomalies may occur in the database if insertion, deletion etc are not
done properly
...
Sharing of Data: In a paper-based record keeping, data cannot be shared among many

users
...


3
...
This increases the reliability of the database as it can be guaranteed that no
wrong data can exist within the database at any point of time
...
Data security: We can restrict certain people from accessing the database or allow them

to see certain portion of the database while blocking sensitive information
...

However, there could be a few disadvantages of using DBMS
...
As DBMS needs computers, we have to invest a good amount in acquiring the hardware,

software, installation facilities and training of users
...
We have to keep regular backups because a failure can occur any time
...

3
...
If someone

can bypass the security system then the database would become open to any kind of
mishandling
Title: Data Base Management System (DBMS)
Description: Introduction to Data Base Management System