Concepts of Database Management System 1st Edition Shefali Naik

Visit ebookfinal.com to download the full version and
explore more ebooks or textbooks
Concepts of Database Management System 1st Edition
Shefali Naik
_____ Click the link below to download _____
https://ebookfinal.com/download/concepts-of-database-
management-system-1st-edition-shefali-naik/
Explore and download more ebooks or textbook at ebookfinal.com

Here are some recommended products that we believe you will be
interested in. You can click the link to download.
Database System Concepts 7th Edition Henry F. Korth
https://ebookfinal.com/download/database-system-concepts-7th-edition-
henry-f-korth/
Concepts of Database Management 8th Edition Philip J.
Pratt
https://ebookfinal.com/download/concepts-of-database-management-8th-
edition-philip-j-pratt/
A History of Indian English Literature 1st Edition M.K
Naik
https://ebookfinal.com/download/a-history-of-indian-english-
literature-1st-edition-m-k-naik/
Modern Database Management 11th Edition Jeffrey A. Hoffer
https://ebookfinal.com/download/modern-database-management-11th-
edition-jeffrey-a-hoffer/

Database Management Systems 2nd Edition Vijay Krishna
Pallaw
https://ebookfinal.com/download/database-management-systems-2nd-
edition-vijay-krishna-pallaw/
Modern Database Management 12th Edition Jeffrey A. Hoffer
https://ebookfinal.com/download/modern-database-management-12th-
edition-jeffrey-a-hoffer/
The New Relational Database Dictionary Terms Concepts and
Examples 1st Edition C. J. Date
https://ebookfinal.com/download/the-new-relational-database-
dictionary-terms-concepts-and-examples-1st-edition-c-j-date/
Management of Retinal Vein Occlusion Current Concepts 1st
Edition Seenu Hariprasad
https://ebookfinal.com/download/management-of-retinal-vein-occlusion-
current-concepts-1st-edition-seenu-hariprasad/
Supervision Concepts and Practices of Management Edwin C.
Leonard Jr
https://ebookfinal.com/download/supervision-concepts-and-practices-of-
management-edwin-c-leonard-jr/

Concepts of Database Management System 1st Edition
Shefali Naik Digital Instant Download
Author(s): Shefali Naik
ISBN(s): 9789332537231, 9332537232
Edition: 1
File Details: PDF, 8.53 MB
Year: 2014
Language: english

CONCEPTS OF
DATABASE
MANAGEMENT
SYSTEM___
_ _ _ _ _ _ SHEFALI NAIK
ALWAYS LEARN I NG PEARSON

Concepts of Database
Management System
Shefali Naik
FM_Final.indd 1 3/18/2014 5:02:47 PM

Dedicated to
My husband Trushit, daughter Jisha, and son Harsheev
FM_Final.indd 2 3/18/2014 5:02:47 PM
Copyright © 2014 Dorling Kindersley (India) Pvt. Ltd.
No part of this eBook may be used or reproduced in any manner whatsoever without the
publisher’s prior written consent.
This eBook may or may not include all assets that were part of the print version. The
publisher reserves the right to remove any material in this eBook at any time.
10 9 8 7 6 5 4 3 2 1
Head Office: 7th Floor, Knowledge Boulevard, A-8(A) Sector 62, Noida 201 309, India.
Registered Office: 11 Community Centre, Panchsheel Park, New Delhi 110 017, India.
ISBN: 9789332526280
e-ISBN: 9789332537231

Contents
Foreword vii
Preface ix
Acknowledgements xi
About the Author xiii
Chapter 1 Basics of Database 1
1.1 Introduction 1
1.2 Data and Information 1
1.2.1 Data 1
1.2.2 Information 2
1.3 Database 5
1.3.1 Components of Database System 6
1.4 Database Management 11
1.5 Database Management System 11
1.6 Need for a Database 12
1.7 File-based Data Management System 12
1.8 Characteristics, or Features, or Advantages
of Database Systems 14
1.9 Limitations of Database 15
Summary 16
Chapter 2 Data Models and Architecture of DBMS 19
2.1 Evolution of Data Models 19
2.2 Hierarchical Data Model 21
2.3 Network Data Model 26
2.4 Relational Data Model 27
2.5 Object-oriented Data Model 30
2.6 Object-relational Data Model 32
2.7 Three Level Architecture of Database 33
2.8 Database Languages 35
2.9 Data and Structural Independence 36
Summary 36
Chapter 3 Relational Database Management System 41
3.1 Introduction 41
3.2 RDBMS Terminology 41
3.3 Various Types of Keys 44
3.4 Integrity Rules 48
FM_Final.indd 3 3/18/2014 5:02:47 PM

iv | Contents
3.5 Relational Set Operators 50
3.6 Retrieval Operators 52
3.7 CODD’s Twelve Rules of Relational Database 53
3.8 Database Life Cycle 54
3.9 Data Dictionary 54
Summary 55
Chapter 4 Developing Entity-Relationship Diagram 59
4.1 Introduction 59
4.2 Identifying Entities 60
4.3 Identifying Relationships 63
4.4 Types of Relationships 63
4.5 Relationship Participation 66
4.6 Strong and Weak Relationship 68
4.7 Managing Many-to-many Relationship 68
4.8 Example of E-R Model 68
4.9 Extended E-R Model 72
4.10 Converting E-R Model into Relational Model 73
4.11 Object Modelling 75
4.11.1 Subclass and Superclass 75
4.11.2 Specialization and Generalization 76
4.11.3 Class Diagram 76
Summary 76
Chapter 5 Normalization82
5.1 Introduction 82
5.2 Need for Normalization 82
5.3 Types of Dependencies 83
5.4 First Normal Form 88
5.5 Second Normal Form 88
5.6 Third Normal Form 94
5.7 Boyce-Codd Normal Form 96
5.8 Multi-valued Dependency 98
5.9 Join Dependency 100
5.10 Lossless and Lossy Decompositions 101
5.11 Normalizing Tables 102
5.12 Examples 103
Summary 108
Chapter 6 Managing Data Using Structured Query Language (SQL) 111
6.1 Introduction 111
6.2 Data Definition Commands 112
6.3 Data Manipulation Commands 114
6.4 SELECT Statement and Its Clauses 115
FM_Final.indd 4 3/18/2014 5:02:47 PM

Contents | v
6.5 Aggregate Functions 118
6.6 Date and Time Functions 119
6.7 String Functions 121
6.8 Conversion Functions 122
6.9 Mathematical Functions 122
6.10 Special Operators 123
6.11 Types of Constraints 125
6.12 Types of Join and Set Operators 127
6.13 Sub-query 128
6.14 Advances SQL Roll-up, Cube, Crosstab 129
Summary 132
Chapter 7 Introduction to PL/SQL 138
7.2 Block of PL/SQL in Oracle 138
7.3 Cursors in Oracle 139
7.4 Procedures in Oracle 142
7.5 Functions in Oracle 143
7.6 Triggers in Oracle 144
7.7 Overview of Packages in Oracle 145
Summary 146
Chapter 8 Transaction Management in Database 148
8.2 Definition of Transaction 148
8.3 Properties of Transaction 152
8.4 States of Transaction 155
8.5 Concurrency Control Using Locks 155
8.6 Deadlocks 158
8.7 Database Backup and Recovery 159
8.8 Security, Integrity and Authorization 161
Summary 161
Chapter 9
Centralized and Distributed Database
Management System 165
9.2 Types of Databases 165
9.3 Centralized Database Management System
vs. Distributed Database Management System 166
9.4 DDBMS Components 169
9.5 Distributed Processing 169
9.6 DDBMS Advantages and Disadvantages 170
Summary 170
FM_Final.indd 5 3/18/2014 5:02:47 PM

vi | Contents
Chapter 10 Advancement in Databases 172
10.1 Multidimensional Database 172
10.2 Mobile Databases 172
10.3 Multimedia Databases 174
10.4 Data Warehousing and Data Mining 174
10.5 Open Source Database 175
10.6 Spatial Databases 175
10.7 Moving Object Databases 176
10.8 NoSQL Database 176
Summary 177
Chapter 11 Overview of MS-Access 2007 180
11.1 MS-Access as an RDBMS 180
11.2 Elements of MS-Access 180
11.3 Creating Database and Tables 181
11.4 Data Types of MS-Access 183
11.5 Sorting and Filtering Records in MS-Access 187
11.6 Creating Queries in MS-Access 188
11.7 Creating Forms in MS-Access 196
11.8 Creating Reports in MS-Access 201
11.9 Creating Macros and Switchboard 205
Summary 211
Chapter 12 Overview of Oracle 221
12.1 Oracle as an RDBMS 221
12.2 Logging into Oracle 221
12.3 Command Summary of Oracle Database 10g XE 222
12.4 Database Administration 228
12.4.1 Managing Users 228
12.4.2 Managing Roles 229
12.4.3 Managing Privileges 231
Summary 233
References and Bibliography 235
Index 243
FM_Final.indd 6 3/18/2014 5:02:47 PM

Foreword
Database Management System is one of the most important subjects of the computer and IT
field. It is used in almost all the applications like management information systems, expert
systems, business information systems, mobile applications, and many more. Over the years, the
world has witnessed many inventions in database technologies. The most important invention
is relational database management system. Application developers, in the IT industry, are using
relational model-based databases for more than thirty years.
Students of IT, computer science and applications, are required to learn databases in one or more
courses. Databases are used to store and retrieve data. There are certain rules used to manage data
within a database. Database provides many features related to data, such as sharing and integration
of data, consistent transaction execution, security and recovery of data through authorization and
algorithms. The relational models use a common language, named as Structured Query Language
(SQL) to process data. With the rise of the Internet and mobile technologies, databases are also
evolving. To store huge amount of data which are spreading worldwide on the Internet and mobile
devices, relational database management systems are not enough. Special types of databases, such
as NoSQL (Not only SQL) are required for managing such data.Apart from NoSQL databases, the
databases which are able to store information related to moving objects, multimedia data, historical
data from multiple dimensions, spatial data, etc., are also needed. Automation of processes also
require maintenance of the existing applications and analysis of historical data. Analysis of histori-
cal data helps in improving business functions by taking important decisions.
In this book, the concepts of databases has been clearly explained giving examples in a lucid
language. All chapters are well-organized and comprehensively covering the syllabus of the
course on Database Management Systems. At the end of each chapter, summary is given to
quickly recap the concepts. The exercises include theory questions, multiple-choice questions,
andquestionsforstudent’spractice.Theoverviewofemergingtrendsindatabasesisthoroughly
explained. This book addresses the need of B.Tech, M.C.A., and IT programme students, faculty
members, and professional developers. I am sure that they will be benefited from this book.
Shefali Naik, the author of this book, is working as senior faculty member, since past thirteen
years, at the School of Computer Studies of the Ahmedabad University. She teaches courses
on database management systems at graduate and post-graduate levels. To her credit, she has
written a good number of articles and technical papers in the area of databases. I wish her good
luck for authoring this book and her academic career.
—Bipin V. Mehta
Director
School of Computer Studies,
Ahmedabad University
FM_Final.indd 7 3/18/2014 5:02:47 PM

Preface
This is the first edition of this book. I have tried to cover all the concepts of database manage-
ment system. This book is useful for the students of computer science, IT, and the courses in
which database is offered as an interdisciplinary subject.
The readers who are new to this subject, can start this book reading from the first chapter.
Those who are already familiar with databases, can read any chapter to know more about it.
Readers, who are willing to learn about any Relational Database Management System, may read
Chapters 11 and 12 which gives brief details on MS-Access and Oracle RDBMS, respectively.
Readers, who are interested in advancement in database, may read Chapters 8, 9 and 10 which
describe advanced topics in database, such as Transactions, Distributed Database, and emerging
trends in Database. Those who wish to learn programming language used in database, may read
Chapters 6 and 7 in which SQL and PL/SQL is discussed.
The details covered in each chapter of this book are as follows:
●
● Chapter 1 gives an overview of database by explaining the basic concepts of database,
such as data, information; database management system’s advantages on other record-
keeping system and limitations, its components, etc.
●
● Chapter 2 describes the evolution of database management system from different sys-
tems, such as hierarchical model and network model. It also describes the architecture of
DBMS.
●
● Chapter 3 explains Relational Database Management System.
●
● Chapter 4 explains Entity-Relationship Model, and Chapter 5 describes Normalization
Process.
●
● Chapters 6 and 7 explains the common languages SQL and PL/SQL, which is used in
relational database systems to create and manage database objects; add, remove, change
and retrieve data to/from tables and write small programs.
●
● In Chapter 8, Transaction is discussed; Chapter 9 explains Centralized and Distributed
database, and Chapter 10 describes advancement in databases.
●
● Chapters 11 and 12 cover two well-known relational database management systems MS-
Access and Oracle.
Any suggestions to improve the content of the book are welcome.
—Shefali Naik
FM_Final.indd 9 3/18/2014 5:02:47 PM

Acknowledgements
I am indebted to many people who were directly or indirectly involved with the creation of
this book.
I would like to thank Bipin V. Mehta, Director at the School of Computer Studies of the
Ahmedabad University, for his inspiration and contribution with the Foreword of this book.
I am grateful to my colleague and friend, Pratik Thanawala, for his technical suggestions
which helped me to improve the contents of this book. I am thankful to my friends from other
universities, Sonal Jain, Shivani Trivedi and Tripti Dodiya, for their guidance.
I would like to acknowledge the assistance provided by the editorial team of Pearson
Education, Noida; especially, Neha Goomer and Nikhil Rakshit, for their continuous assistance
in solving various queries related to the publishing of this book. I am also thankful to Uma
Tamang and Naresh Sharma. A big thanks to Pearson Education for publishing this book.
I thank my parents, Girish and Bharati Naik, and children, Jisha and Harsheev along with
rest of the family, for their love and patience. Finally, I owe it to my husband Trushit, for his
constant support and encouragement.
—Shefali Naik
FM_Final.indd 11 3/18/2014 5:02:47 PM

About the Author
Mrs Shefali Naik, the author of this book, is working as a senior faculty member for past 13 years
at School of Computer Studies, Ahmedabad University, Ahmedabad. She teaches subjects related
to Databases, Programming, Systems Analysis and Design, and Software Project Management
at undergraduate and post-graduate levels. She has obtained her Master’s degree in Computer
Applications (M.C.A.) and Bachelor’s degree in science with mathematics as a special subject
(B.Sc., Mathematics) from Ahmedabad, Gujarat.
The author has written few technical papers and articles in the area of databases.
Presently, she is pursuing her Ph.D. from S.P. University,VallabhVidyanagar,Anand, Gujarat,
in the subject of Distributed Databases.
FM_Final.indd 13 3/18/2014 5:02:48 PM

CHAPTER
1.1 | Introduction
In the current era, people of all ages use database in one way or the other. Everyone uses
database in different ways. For example, school children use database of e-mail programs and
mobile phones, youngsters use online movie and railway ticket booking database to book tick-
ets, housewives use database of books to order books online or access various community site’s
database, businessmen use database of airlines to book their trips, academicians use online
journals database to do research work and many more. Nowadays, computers are used every-
where. We may reform the proverb ‘Where there is a will, there is a way!’ as ‘Where there
is a computer, there is a database.’ Computerized Databases have made our life very easy and
comfortable. We can search any place, product, area, thing, etc., with the help of stored data in
a fraction of a second. Stored data processed with the help of database management systems
extracts the desired information, every time. Let us understand the database in some more detail.
1.2 | Data and Information
1.2.1 | Data
Data is a plural of word ‘datum’. In our daily life, we use the word data to describe facts about
any person, event, place or thing. Data are raw facts which may be numbers, values, names,
1
Basics of Database
• Understanding the meaning of data and information.
• Knowing how database and database management systems are useful in organizations to keep
records.
• Examples of database management system.
• Components of database system.
• Characteristics of data and DBMS.
• Differences between file-based management systems.
• Limitations of DBMS.
Chapter Objectives
CH_1_Basics of Database_Final.indd 1 2/26/2014 3:36:03 PM

2 | Chapter 1
dates, etc. When we combine related data, they describe any real-world entity. Related data
means data which belong to the same entity (person, place, event or thing). For example, If
we consider the entity ‘Doctor’ (person type of entity), then doctor’s name, doctor’s address,
doctor’s birth date, doctor’s qualification, doctor’s specialization, etc., are data related to
doctor. We cannot say that supplier’s name and doctor’s qualification are related data;
because both describe two different entities named supplier and doctor. Thus, when we want
to describe any real-world entity, we use data values. Data values alone do not have any
meaning because they are not processed yet.
1.2.2 | Information
When we process related data it gives some information. Information is useful to take deci-
sions, it can be stored for future use, it has some meaning. To obtain information, we need data.
For example, when we process students’ attendance data, we can get a list of students with low
attendance, students who are attending lectures regularly, students who come to college to at-
tend particular lectures, pattern of class bunking for each student, etc.
On the basis of this information, the college may decide the attendance policy, reschedule
the time-table to improve attendance, decide whether to inform parents or not, determine which
students should be allowed to sit for an examination, etc. This information could also be stored
for future use. In case, when students need a transcript, this information can be used to fill up
lecture-wise attendance details of each student or to generate attendance certificates which may
be required along with migration certificates when students change universities.
Data can be stored manually or electronically. Similarly, stored data may be processed manu-
ally or electronically. Table 1.1 shows some examples of data and information.
We can show the relationship between data and information as given in Figure 1.1.
Figure 1.2 shows an example of data and information.
Table 1.1 shows some examples of data, processes which should be applied on stored data
and information which could be obtained after processing certain data.
Table 1.2 shows a student’s examination result data which can be processed as per the follow-
ing condition to obtain grade-wise Result analysis.
Table 1.1 | Examples of Data and Information
Data Process Description Information
Census data Sort records based on area and count
total no. of persons gender-wise and
age group-wise
Area-wise male and female
ratio for different age groups
Board Exam Data Count subject-wise, no. of students
who passed or failed in an exam
Subject-wise total no. of passed
or failed students
Climate Data Maximum temperature and minimum
temperature during the year
Hottest and coldest day of the
year

Basics of Database | 3
If percentage 40 then, Grade = ‘F’
If percentage ≥ 40 and 50 then, Grade = ‘D’
If percentage ≥ 50 and 60 then, Grade = ‘C’
If percentage ≥ 60 and 70 then, Grade = ‘B’
If percentage ≥ 70 then, Grade = ‘A’
The following sample information may be obtained after processing the data given in Table 1.2:
Class-wise Result Analysis
Table 1.2 | Students’ Examination Result Data
Std No. Class Code Std Name Percentage Gender
1 FY Mitali Gupta 89 Female
2 FY Nirav Valera 91 Male
3 FY Jainam Vora 79 Male
4 FY Rajani Vyas 57 Female
5 FY Nidhi Jain 64 Female
1 SY Kartik Bhatt 82 Male
2 SY Kanika Yadav 84 Female
3 SY Karishma Yadav 70 Female
4 SY Siddharth Soni 39 Male
5 SY Akash Patel 69 Male
1 TY Paras Sanghvi 84 Male
2 TY Pankti Bindal 94 Female
3 TY Richa Singh 75 Female
4 TY Neel Shah 59 Male
5 TY Payal Shah 60 Female
Process
Data Information
Figure 1.1 | Relationship between data and information.
Students’ Attendance Data
Percentage of lectures attended by student
Total no. of lectures attended × 100
Total no. of lectures conducted
Data
Process
Information
Figure 1.2 | Example of data and information.

4 | Chapter 1
Class code: FY
No. of students who got ‘A’ Grade: 3
No. of students who got ‘B’ Grade: 1
No. of students who got ‘C’ Grade: 1
No. of students who got ‘D’ Grade: 0
No. of students who got ‘F’ Grade: 0
Class code: SY
Class code: TY
Overall total no. of students who passed in the exam:14
Overall total no. of students who failed in the exam:1
The above information may be stored and processed further to represent the result analysis
graphically or pictorially using bar charts as represented in Figure 1.3. X-axis will contains
class code and grades, and Y-axis contains total number of students.
1 1 1 1
1 1
0 0 0 0 0 0
FY
3
2.5
1.5
0.5
0
1
2
SY TY
3
3
3
A
B
C
D
E
Figure 1.3 | Bar chart represents class-wise grade-wise total number of students.

1.3 | database
As the name suggests, database is a collection of data, i.e., database is a storage area where we
can store all related data and process them. To understand the concept of database, let us take
some real-time examples of database (storage). One logical database which we carry with us
all the time is our brain. The brain stores all thoughts, ideas and things which we learn, view,
etc. and it relates them. We can retrieve, change or remove these stored ideas and thoughts any
time. The example of real-time physical database is a grain warehouse. When it is the season
for some grain/pulses, we store them and use them later as per the process requirements. When
we process the grains/pulses we obtain the information in the form of floor, sprouts, etc., which
could be used in further processing to cook food. The pulses/grains which we find useless could
be removed from the warehouse and could be replaced (updated) with fresh stock. In real-life,
we use the concepts of data, information and database everywhere.
Figure 1.4 shows an example of real-life database of children’s’ schoolbag. It is a stationery
database which contains entities such as notebook, textbook, compass box, geometry case, etc.
Entity Notebook has distinguished notebooks of various subjects; Entity Textbook has distin-
guished textbooks of various subjects; Entity Compass box has pencils, erasers, sharpeners,
ruler, etc., and Entity Geometry box has common mathematical tools.
A database is like an electronic storage, which contains computerized data files (entities).
It can contain one or many data
files. Data files contain various
related data within it. Database
should contain accurate, con-
sistent and non-redundant data
which could be shared by differ-
ent application programs. Data
can be related by defining rela-
tionships between proper data.
Also, conditions (constraints)
may be applied on data. Different
users may access different data
sets from the same database by
writing application program. We
may put security and authentica-
tion procedures to provide autho-
rised access of data. There may be
more than one database within a
database management system. All
related entities are kept together
in the same database. Data within database can be retrieved, updated or deleted directly by
database administrator or by authorized users or application programs written by users. To
describe data, other details are stored along with the data such as data type, size, constraints,
description, format, etc. Using this information, the database management software generates
data dictionary which contains ‘data about data’ or ‘metadata’.
Schoolbag: A database
of stationery items
Notebook: An entity
within a database
Geometry box: An
entity within a database
Compass box: An
entity within a database
Textbook: An
entity within a
database
Geometry box: An
fIGure 1.4 | Real-life example of a database.

6 | Chapter 1
Database contains data stored in computer. To process the stored data, we need application
programs. The processed data could be again stored into database for future use. The data, on
which we can do some processing, is known as operational data. Any organization contains
operational data. Table 1.3 contains some examples of organizations and operational data of a
particular organization.
A database stores data of various entities. These entities can be related using relationships.
Data also contains description, which is known as metadata. Along with the data, one can keep
constraints on its data types.
A cylindrical shape, as shown in Figure 1.5, is used to represent physical database. Physical
database is useful for the computer (i.e., how a machine sees data), while logical database is
useful for the user (i.e., how a human being sees data). It is a database of a university, which
contains various related entities, such as course, college, student, class, attendance, exam, etc.
There are many colleges in a university; each college contains many students in different courses
and classes. Students attend lectures, appear in exams and get results.
The ‘University’ database contains interrelated data which could be shared by different ap-
plication programs to obtain meaningful information.
1.3.1 | Components of Database System
Figure 1.6 shows components of any conventional database system.
1. User: User is any person who uses a database or any other object of the database. User
may be of different types and at different levels in an organization. Say for example, the
‘University’ database may be useful for different persons who are directly or indirectly as-
sociated with the university. Following are some categories of users who may use database.
Figure 1.5 | Example of ‘University’ database.
College
Attendance Class
Exam
Student
Course
Table 1.3 | List of Some Organizations and Related Operational Data
Organization Operational Data
Public Library Member data, Books data, Publisher data, etc.
Restaurant Customer data, Employee data, Food Items data, etc.
Super Mall Product data, Customer data, Supplier data, etc.
University Student data, Faculty data, Exam data, etc.
Hospital Patient data, Doctor data, etc.

a. Naive User, or End-user, or Layman: The clerk of the university uses the ‘university’
database to enter the data of applicants who have applied for various courses and the
same data are retrieved to generate a merit list. The clerk does not know anything about
the technical features of the database or the language, using which data is entered or
retrieved. He is completely unaware about the technology. Therefore, he/she is known as
an end-user or Layman or Naive user. Table 1.4 shows some examples of databases and
end-users of that database.
b. Software Programmer, or Application Programmer, or Application Developer: A soft-
ware programmer is a person who writes application programs or logic in some specific
language to insert, delete, update or fetch data to/from database. An application program-
mer has brief knowledge about database and Query Language which is used for writing
programs. Query Language is a generalized language which is available with all data-
bases. A programmer may or may not have deep understanding about database concepts,
but he/she is able to operate on data stored in the database.
Table 1.4 | Examples of End-users
Database End-user
Online University Database Applicants, Parents, University Staff, etc.
Hotel database Customer, hotel Employees, etc.
Online Railway Reservation
Database
Citizens of the country, Agents, Railway
officials, etc.
Figure 1.6 | Components of database system.
Datafile 1 Datafile 2
Data 1
Data 1
Data 2
Data 2
Data 2
D
a
t
a
f
i
l
e
1
D
a
t
a
f
i
l
e
2
Data2
D
a
t
a
2
D
a
t
a
f
i
l
e
2
D
a
t
a
1
D
a
t
a
2
D
a
t
a
1
User(Software
programmer)
writes programs
to view data
User(DBA) writes
validation programs
and manages
security on
Hardware on which
database is stored
Programs
programs
programs
Programs
programs
programs
Programs
Programs
Datafile 2

8 | Chapter 1
c. Database Designer: A database designer decides about entities (data files) which should
be stored within database, constraints to be applied on data, data types, format and
other specifications regarding data. The database designer is responsible for designing
of data files.
d. Database Administrator: A database administrator (DBA) is the person who is the over-
all in-charge of a database. He/she assigns authorization to users, writes validation proce-
dures, decides backup and recovery policies, and manages users and privileges. In short,
DBA keeps control on database.
2. Hardware: Hardware is a permanent storage where the database is stored. It may be a
hard-disc, or any other secondary memory. One single database may be stored on more
than one storage devices depending on the volume of data stored within the database. For
security purpose, a copy of database could be kept on some other storage device. Besides
storage device, other hardware, such as computer, peripherals, etc., are also required to
perform database-oriented operations.
3. Software (data dictionary management, database schema management, SQL):
Software are programs or applications which are used to access data from database.
These applications reside in DBMS or there may be some applications which could be
interfaced with DBMS to manage data. For example, programming languages are used
to display data on monitor. There are some software programs, which are part of DBMS,
that manage data dictionary or metadata, define schema for the database objects, and are
used to write query on database. The common language available with all the databases
is known as Structured Query Language; if which is popularly known as SQL and
sometimes pronounced as ‘Sequel’.
4. Data: Data is the most important component of a database system. Data is discussed in
detail in Section 1.1. When data is stored in database, it should be stored along with its
definition, data type and size, constraints, such as duplicate values are allowed or not,
possible range of values, formula if it is derived from some other data, etc., display format,
format in which it should be entered, validation rules, etc. Some examples of data
files/entities (tables) and data stored within the entity are given in Tables 1.5, 1.6 and 1.7.
These data files are inter-related data files which are part of the playschool’s database.
Table 1.5 | Example of Data within Data File ‘Kindergarten’
Data Name Data Type (Size) Constraint Input Format Display Format
Data File Name: Kindergarten
KG id Integer Unique number which
Should be generated
automatically.
— —
KG name Character(30) Must be entered. Should be entered
in upper case.
Should be dis-
played in title
case.
Address Character(100) — — —
No. of branches Integer ≥0 — —
Contact no. Integer — — —
Contact person Character (20) — — —

Table 1.6 | Example of Data within Data File ‘Class’
Data File Name: Class
Class code Character (3) Must be entered Should be entered
in upper case.
Should be displayed
in upper case.
Class desc. Character (30) — — —
Class capacity Integer 0 and ≤30 — —
No. of divisions Integer 0 and ≤4 — —
Age criteria Float ≥2 — —
Table 1.7 | Example of Data within Data File ‘Class’
Data File Name: Kindergarten Detail
Class code Character(3) Must be entered Should be entered
in upper case.
Should be displayed
in upper case.
KG id Integer Must be entered — —
Division Character(1) Upper case — —
No. of students Integer 0 and ≤30 — —
Table 1.8 | Example of Data Values within Data File ‘Kindergarten’
KG ID KG Name Address No. of Branches Contact No. Contact Person
Data File Name: Kindergarten
1 Innocent
Flower
Naranpura,
Ahmedabad
1 27417411 Mr S. T. Pandya
2 Smart Kids Navrangpura,
Ahmedabad
3 27477471 Ms K. P. Verma
3 Kids Zone Satellite,
Ahmedabad
4 26306301 Mr A. R. Nair
4 Teacher’s Pet Naranpura,
Ahmedabad
2 27567561 Mr T. R. Khanna
5 Little Star Ambawadi,
Ahmedabad
1 26466461 Ms N. J. Gupta
When data are entered into tables, Kindergarten, Class and Kindergarten Details (Tables 1.5,
1.6 and 1.7 respectively); the correctness of data are checked. Invalid data cannot be entered
into data files.
Tables 1.8, 1.9 and 1.10 contain some valid data values for the tables Kindergarten, Class and
Kindergarten Details, respectively.

Discovering Diverse Content Through
Random Scribd Documents

payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”
• You provide a full refund of any money paid by a user who
notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of
any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project
Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend
considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright

law in creating the Project Gutenberg™ collection. Despite these
efforts, Project Gutenberg™ electronic works, and the medium
on which they may be stored, may contain “Defects,” such as,
but not limited to, incomplete, inaccurate or corrupt data,
transcription errors, a copyright or other intellectual property
infringement, a defective or damaged disk or other medium, a
computer virus, or computer codes that damage or cannot be
read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except
for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU AGREE
THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT
LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT
EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE
THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you
discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person
or entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.

If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.
1.F.4. Except for the limited right of replacement or refund set
forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied
warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the
Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you
do or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.
Section 2. Information about the Mission
of Project Gutenberg™

Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the
assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.
Section 3. Information about the Project
Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status
by the Internal Revenue Service. The Foundation’s EIN or
federal tax identification number is 64-6221541. Contributions
to the Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.
The Foundation’s business office is located at 809 North 1500
West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact

Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws
regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or determine
the status of compliance for any particular state visit
www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states
where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot
make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.
Please check the Project Gutenberg web pages for current
donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and

credit card donations. To donate, please visit:
www.gutenberg.org/donate.
Section 5. General Information About
Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.
Project Gutenberg™ eBooks are often created from several
printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,
including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.

Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
Let us accompany you on the journey of exploring knowledge and
personal growth!
ebookfinal.com

Concepts of Database Management System 1st Edition Shefali Naik

More Related Content

Similar to Concepts of Database Management System 1st Edition Shefali Naik

Recently uploaded

Concepts of Database Management System 1st Edition Shefali Naik