Database System: Concepts and Design: December 2003
Database System: Concepts and Design: December 2003
Database System: Concepts and Design: December 2003
net/publication/257298522
CITATIONS READS
0 194,296
1 author:
Bhojaraju Gunjal
National Institute of Technology Rourkela
61 PUBLICATIONS 133 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
Access and Usage of E-Journals by Research Scholars in National Institute of Technology (NIT) Rourkela, Odisha: A Case Study View project
A study on The Global Competitiveness of Indian Rubber Industry: Non-Tyre Sector View project
All content following this page was uploaded by Bhojaraju Gunjal on 05 February 2014.
Mr.Bhojaraju G.*
Dr.M.M.Koganurmath**
Synopsis:
1. Introduction to Database
1.1 Meaning and Definition of Database
1.2 Functions of Database
1.3 Types of Databases
1.3.1 Bibliographic Database
1.3.2 Knowledge Database
1.3.3 Graphic-Oriented Database
1.3.4 Decision-making Database
1.4 Concept of Data Structure
1.4.1 List Structure
1.4.2 Tree / Hierarchical Structure
1.4.3 Network Structure
2. Introduction to DBMS
2.1 Objectives of DBMS
2.2 Functions of DBMS
2.3 Components to DBMS
2.4 Advantages and Disadvantages of DBMS
3. Database Design
3.1 Goals of Database Design
3.2 Logical and Physical View of Database
3.3 View of Data / Architecture of Database System
3.2.1 Data Abstraction
3.2.2 Instances and Schemas
3.2.3 Data independence
3.2.4 Database Languages
3.4 Storage Structures
3.5 Phases in Database Design
1
Database System : Concepts and Design
* Librarian , Fr.C.Rodrigues Institute of Technology, Sector 9A,Vashi, Navi Mumbai - 400 703.
**Librarian, Tata Institute of Social Sciences, Deonar, Mumbai – 400 088.
2
Database System : Concepts and Design
3
Database System : Concepts and Design
Data independence : means it allows for changes at one level of the database without
affecting the other levels i.e. changing hardware and storage procedures or adding
new data without having to rewrite application program.
Economy (i.e. more information at low cost) : Using, storing and modifying data at
low cost are important.
Accuracy and integrity : Even if redundancy is eliminated, however, the database
may still contain incorrect data. Centralized control of the database helps in avoiding
these situation. The accuracy of a database ensures that data quality and content
remain constant. Integrity controls detect data inaccuracies where they occur.
Recovery from failure : With multi-user access to a database, the system must
recover quickly after it is down with no loss of transactions. It helps to maintain data
accuracy and integrity.
Privacy and Security : For data to remain private, security measures must be taken
to prevent unauthorized access i.e. complete jurisdiction over the operational data.
DBMS ensures proper security through centralized control.
Performance : It emphasizes response time to inquiries suitable to the use of the data
depends on the nature the user-database dialogue.
Database retrieval, analysis, storage :.It facilitates Database retrieval, analysis and
storage.
Compatibility : Usefulness i.e. hardware/software can work with different
computers.
Concurrency control : is a feature that allows simultaneous access to a database,
while preserving data integrity.
Support : Support of complex file structure and access path. Ex : MARC
Data Sharing : A database allows sharing of data under its control by any number of
users.
Standards can be enforced : Standardizing stored data formats is particularly
desirable as an aid to data interchange between systems.
1.3 Types of Databases :
Database is considered as a central pool of data which can be shared by a
community of users. There are three yard sticks to determine the nature of data we can
deal with. They are :
a. Whether data is free of format or whether it is formatted.
b. Whether definition of data is of the same size as data itself.
c. Whether the data is active or passive.
Whether these yard sticks are applied to data. We can classify database into four kinds
which are
1.3.1 Bibliographic Databases
1.3.2 Knowledge Databases
1.3.3 Graphic-Oriented Databases
1.3.4 Decision-making Databases
4
Database System : Concepts and Design
1.3.1 Bibliographic Databases : have data which is free of format (unformatted data).
They are composed of textual data which, by it's very nature, displays little or no format.
Such databases are often used in Library and information system. Here data could be
composed of abstracts of books and such documents with key words and key phrases.
Through the abstract, one can determine the document is of interest or not. Bibliographic
database contains descriptive information about documents, titles, authors, Journal name,
Volume and Number, date, keywords, abstract, etc.
1.3.2 Knowledge Databases : are used in Artificial Intelligence applications. The data
contained in these is discrete and formatted. In these there are typically many kinds of
data, with only a very few occurrence of each kind. Such databases having the size of the
data is as large as the definition of the data.
1.3.3 Graphic-Oriented Databases : could possibly used in Computer-Aided Design
(CAD). The data in such database is characterized as being active. This means that data is
a procedure capable of being executed. Any modification can be made in data, as the
above 1 and 2 cannot be executed in a computer.
Ex : Computer-Aided Design (CAD)
Computer-Aided Learning (CAL)
Computer-Aided Instruction (CAI)
1.3.4 Decision-making Databases : are used in corporate management and allied
administrative tasks. Using data contained in these databases, one could handle problem
like resource planning and sales forecasting. These databases are characterized by the fact
and their data contents are :
a. Formatted
b. Far longer than description
c. Passive
These Decision-making databases are often referred to as just databases.
Depending upon the kind of databases being handled Database Management Systems
(DBMS) can be classified as for example : Bibliographic Database Management Systems,
Knowledge Database Management Systems and so on.
1.4 Concept of Data Structure :
Data are structured according to the Data model. A group of data elements handled
as a unit. Ex : Book details - is a data structure consisting of the data elements - Author
name, Title, Publisher's name, ISBN and Quantity.
There are several different approaches to analyzing the logical structure of data in
complex databases. Although all DBMS's have a common approach to data management,
they differ in the way : the structure of data.
There are three types of data structure, viz
1.4.1 List Structure
1.4.2 Tree / Hierarchical Structure
1.4.3 Network Structure
5
Database System : Concepts and Design
1.4.1 List Structure : A list is nothing morethan a special data structure made up of data
record where the Nth record is related (N-1) and (N-2) simply because of positioning.
This brings one-to-one relationship. This structure is illustrated as below :
6
Database System : Concepts and Design
7
Database System : Concepts and Design
8
Database System : Concepts and Design
9
Database System : Concepts and Design
In database design, several views of data must be considered along with the
persons who use them. There are three views :
1. The overall logical view
2. The program logical view
3. Physical view
The logical view is what the data look like, regardless of how they are stored
whereas the
physical view is the way data exist in physical storage, it deals with how data are stored,
accessed or related to other data in storage.
Four views of data : THREE logical views and ONE physical view.
The logical view as the user's view, the programmer's view and the overall logical
view (schema).
The overall logical view (schema) helps the DBMS to decide what data in storage
it should act upon as required by the application program.
A DBMS is a collection of interrelated files and a set of programs that allow users
to access and modify these files. A major purpose of a database system is to provide users
with an abstract view of the data i.e. the system hides certain details of how the data are
stored and maintained.
3.3 An Architecture for a Database System :
3.3.1 Data Abstraction : Many database system users are not computer trained,
developers hide the complexity from users through several level of abstraction, to
simplify users' interaction with the system. The architecture is divided into three general
levels : internal, conceptual and external.
10
Database System : Concepts and Design
a. Internal / Physical level : The internal level is the one closest to physical storage i.e.
one concerned with the way in which the data is actually stored. It is the lowest level of
abstraction describes how the data are actually stored. At the physical level, complex low
level data structures are described in detail.
b. Conceptual / Logical level : is a "level of indirection" between the internal and
external. The next higher level of abstraction describes what data are stored in the
database, and what relationships exists among those data. The entire database is thus
described in term of a small number of relatively simple structures. This level is used by
Database Administrators(DBA), who must decide what information is to be kept in the
database.
c. External / View level : The external level is the one closest to the users, i.e. the one
concerned with the way in which the data is viewed by individual users. It is the highest
level of abstraction describes only part of the entire database. Despite the use of simpler
structures at the logical level, some complexity remains, because of the large size of the
database. Many users of the database system will not be concerned with all this
information. Instead, such users need to access only a part of the database so that their
interaction with the system is simplified, the view level of abstraction is defined. The
system may provide many views for the same database.
If the external level is concerned with the individual user views, the conceptual
level may be thought of as defining a community user view. In other words, there will be
many "external views," each consisting of a more or less abstract representation of some
portion of the database, and there will be a single "conceptual view," consisting of a
similarity abstract representation of the database in its entirety. Likewise, there will be a
single "internal view," representing the total database as actually stored.
11
Database System : Concepts and Design
12
Database System : Concepts and Design
The DBMS is the software that handles all access to the database. Conceptually
what happens is the following :
1. A user issues an access request, using some particular Data Manipulation
Language(DML);
2. the DBMS intercepts the requests and interprets it;
13
Database System : Concepts and Design
3. the DBMS inspects, in turn the external schema, the external/conceptual mapping, the
conceptual schema, the conceptual/internal mapping, and the storage structure definition;
and
4. the DBMS performs the necessary operations on the stored database.
3.4 Storage Structures :
Storage Structures describes the way in which data may be organized in secondary
storage i.e. direct access media such as disk packs, drums and so on.
User operations are expressed (via the DML) in terms of external records, and
must be converted by the DBMS into corresponding operations on internal or stored
records. These later operations must be converted in turn to operations at the actual
hardware level, i.e. to operations on physical record or blocks. The component
responsible for this internal/physical conversion is called an access method. Its function
is to conceal all device-dependent details from the DBMS and to present the DBMS with
a stored record interface. The stored interface thus corresponds to the internal level, just
as the user interface corresponds to the external level. The Physical record interface
corresponds to the actual hardware level.
The stored record interface permits the DBMS to view the storage structure as a
collection of stored files, each one consisting of all occurrences of one type of stored
record(see architecture of DBMS).Specifically, the DBMS knows (a). what stored files
exist, and, for each one, (b) the structure of the corresponding stored record, (c) the stored
field(s), if any, on which it is sequenced, and (d) the stored field(s), if any, that can be
used as search arguments for direct access. This information will all be specified as part
of the storage structure definition.
14
Database System : Concepts and Design
3.5.2 Second phase : The second phase focuses on the design of the database model that
will support organization operations and objectives.
In this phase, we can identify six main phases of the database design :
I. Requirements collection and analysis
II. Conceptual database design
III. Choice of DBMS
IV. Data model mapping
V. Physical database design
VI. Database system implement
15
Database System : Concepts and Design
16
Database System : Concepts and Design
iv. Distributed Database Design : A distributed database stores logically related data
into two or more physically independent sites connected via a computer network. Design
portions of a database may reside in different locations. Processes that access the
database may also vary from one location to another.
II. DBMS Software selection : The selection of DBMS software is critical to the
information systems' smooth operation. Consequently, the proposed DBMS software's
advantages and disadvantages should be carefully studied. The end user must be made
aware of the limitations of both the DBMS and the database in order to avoid false
expectations.
Factors affecting the purchasing decision of DBMS are :
(i).Cost, (ii). DBMS features and tools, (iii). Underlying data model, (iv). Portability, and
(v). DBMS hardware requirements.
III. Logical Design : Logical design is used to translate the Conceptual design into the
internal model for a selected DBMS (such as DB2, SQL Server, Oracle, IMS, Informix,
Access, Ingress and so on). Logical Design follows the decision to use a specific database
model (hierarchical, network or relational ). Once the database model is identified, we
can map the Conceptual design onto a Logical design that is tailored to the selected
database model. At this stage, the logical design is Software dependent. This includes
mapping all objects in the model to the specific constructs used by the selected database
software. The right to use the database is also specified during the logical design phase.
In short, the logical design translates the software independent conceptual model
into a software dependent model by defining the appropriate domain definitions, the
required tables and the necessary access restrictions.
IV. Physical Design : The stage is now set to define the physical requirements that allow
the system to function within the selected hardware environment.
Physical design is the process of selecting the data storage and data access
characteristics of the database. The storage characteristics are a function of the types of
devices supported by the hardware, the type of the data access methods supported by the
system and the DBMS. Physical design affects not only the location of the data in the
storage device(s) but also the performance of the system.
V. Database system implement : After the database has been created, the data must be
loaded into the database tables. If the data are currently stored in a format different from
the required by the new DBMS, the data must be converted prior to being loaded.
During the implementation and loading phase, we also must address performance,
security, backup and recovery, integrity, company standards and concurrency control.
4. Application of DBMS to Library and Information System :
There are two software packages related to Library and Information System. viz.
4.1 DBase III Plus : is one of the most popular DBMS on personal computers. It is the
third major version of the classic dBase database management system series from
Ashton Tate. It is powerful and flexible system for storing, organizing, analyzing and
17
Database System : Concepts and Design
6. References :
1. Rob,Peter and Coronel Carlis : Database Systems: Design, implementation and
management -
4th ed. Cambridge, Course Technology, 2000 (p 1-55,286-321)
2. Date, C J : An Introduction to Database Systems - 3rd ed. Vol. 1
New Delhi: Narosa,1996 (p 3-32,33-61,63-80)
3. Silberschatz,Abraham and others: Database System Concepts - 3rd ed.
New Delhi: McGraw Hill, 1996(p 1-21)
4. Desai,Bipin C : An Introduction to Database Systems
New Delhi: Galgotia, 1996 (p 2-33)
18
Database System : Concepts and Design
19