0% found this document useful (0 votes)
18 views

Database System Environment, Purpose of Database System, View of Data-1

Uploaded by

mishravivek3500
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views

Database System Environment, Purpose of Database System, View of Data-1

Uploaded by

mishravivek3500
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Unit-1

Introduction to Database System


(Database System Environment, Purpose of Database System, View of Data)

Dr. Virendra Singh Kushwah


Senior Assistant Professor Grade-I
School of Computing Science and Engineering
[email protected]
DBMS
• A database-management system (DBMS) is a
collection of interrelated data and a set of programs
to access those data. The collection of data, usually
referred to as the database, contains information
relevant to an enterprise. The primary goal of a DBMS
is to provide a way to store and retrieve database
information that is bot convenient and efficient.
Applications of DBMS
• Banking
• Airlines
• Industries
• Universities
• Sales
• Marketing
• Finance
• Telecommunication
Database Systems versus File Systems
Database System Environment

▪ Hardware

▪ Software
- OS
- DBMS
- Applications

▪ People
▪ Procedures
▪ Data
• New application programs are added to the system as the need
arises. For example, suppose that a university decides to create a
new major (say, computer science).
• As a result, the university creates a new department and creates
new permanent files (or adds information to existing files) to
record information about all the instructors in the department,
students in that major, course offerings, degree requirements, etc.
The university may have to write new application programs to deal
with rules specific to the new major.
• New application programs may also have to be written to handle
new rules in the university. Thus, as time goes by, the system
acquires more files and more application programs.
• This typical file-processing system is supported by a
conventional operating system.
• The system stores permanent records in various files, and it
needs different application programs to extract records from,
and add records to, the appropriate files.
• Before database management systems (DBMSs) were
introduced, organizations usually stored information in such
systems.
Purpose of Database System
• Keeping organizational information in a file-processing system has a
number of major disadvantages:

1. Data redundancy and inconsistency


2. Difficulty in accessing data
3. Data isolation
4. Integrity problems
5. Atomicity problems
6. Concurrent-access anomalies
7. Security problems
Purpose of Database System
• Keeping organizational information in a file-processing system has a
number of major disadvantages:

1. Data redundancy and inconsistency


2. Difficulty in accessing data
3. Data isolation
4. Integrity problems
5. Atomicity problems
6. Concurrent-access anomalies
7. Security problems
View of Data
• A database system 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.
• That is, the system hides certain details of how the
data are stored and maintained.
1. Data Abstraction
The view level of abstraction
exists to simplify their
interaction with the system.
The system may provide many
views for the same database.

The next-higher level of


abstraction describes what data
are stored in the database, and
what relationships exist among
those data.

The lowest level of


abstraction describes
how the data are
actually stored.
2. Instances and Schemas
• Databases change over time as information is inserted and deleted. The
collection of information stored in the database at a particular moment is
called an instance of the database.
• The overall design of the database is called the database schema.
Schemas are changed infrequently, if at all The concept of database
schemas and instances can be understood by analogy to a program
written in a programming language.
• A database schema corresponds to the variable declarations (along with
associated type definitions) in a program. Each variable has a particular
value at a given instant. The values of the variables in a program at a
point in time correspond to an instance of a database schema.
• Database systems have several schemas, partitioned
according to the levels of abstraction.
• The physical schema describes the database design at
the physical level, while the logical schema describes
the database design at the logical level.
• A database may also have several schemas at the view
level, sometimes called subschemas, that describe
different views of the database.

You might also like