IE - DBMS - Module 1
IE - DBMS - Module 1
Dept Of ISE,DSCE 1
Course objectives
Dept Of ISE,DSCE 2
Course Outcomes
Dept Of ISE,DSCE 3
TEXT BOOKS
Dept Of ISE,DSCE 4
UNIT 1- INTRODUCTION
• Database
• Data
• Examples
• Properties of database
– DB represents mini world
– Logically coherent collection of data
– Data for specific purpose
Dept Of ISE,DSCE 5
UNIT 1- INTRODUCTION
• A database has
– some source from which data is derived,
– some degree of interaction with events in the
real world,
– and an audience that is actively interested in
its contents.
• A database can be of any size and
complexity
• A database may be generated and
maintained manually or it may be
Dept Of ISE,DSCE 6
UNIT 1- INTRODUCTION
Dept Of ISE,DSCE 7
UNIT 1- INTRODUCTION
• Defining a database :
– specifying the data types, structures, and constraints of the
data to be stored in the database.
• Constructing the database:
– storing the data on some storage medium that is controlled
by the DBMS.
• Manipulating a database:
– includes functions such as querying the database to retrieve
specific data, updating the database to reflect changes in
the miniworld, and generating reports from the data
• Sharing a database:
– allows multiple users and programs to access the database
simultaneously
Dept Of ISE,DSCE 8
UNIT 1- INTRODUCTION
• Application program
– accesses the database by sending queries or
requests for data to the DBMS.
• A query
– causes some data to be retrieved
• A transaction
– causes some data to be read and some data
to be written into the database.
Dept Of ISE,DSCE 9
UNIT 1- AN EXAMPLE
Dept Of ISE,DSCE 10
UNIT 1- AN EXAMPLE
Dept Of ISE,DSCE 11
AN EXAMPLE
• Design of a new application for an existing database or
design of a brand new database starts off with a phase
called requirements specification and analysis.
• These requirements are documented in detail and
transformed into a conceptual design that can be
represented and manipulated using some computerized
tools .
• The design is then translated to a logical design that can
be expressed in a data model implemented in a
commercial DBMS.
• The final stage is physical design, during which further
specifications are provided for storing and accessing the
database
Dept Of ISE,DSCE 12
Characteristics of the Database Approach
• In traditional file processing, each user defines
and implements the files needed for a specific
software application as part of programming the
application.
• Example:
1. Grade reporting office : students & their grades
2. Accounting office: Students fees and payments
• Both users- interested in same data( student
data), maintains different files.
• Redundancy occurs.
Dept Of ISE,DSCE 13
Characteristics of the Database Approach
Dept Of ISE,DSCE 14
Self-Describing Nature of a Database System
Dept Of ISE,DSCE 16
Insulation between Programs and Data, and
Data Abstraction
• In traditional file processing, the structure of
data files is embedded in the application
programs.
• The structure of data files is stored in the DBMS
catalog separately from the access programs –
called as Program – Data independence
Dept Of ISE,DSCE 17
Insulation between Programs and Data, and Data Abstraction
Dept Of ISE,DSCE 18
Insulation between Programs and Data, and Data Abstraction
Dept Of ISE,DSCE 21
Sharing of Data and Multiuser Transaction Processing
Dept Of ISE,DSCE 23
Advantages of Using the DBMS Approach
Dept Of ISE,DSCE 24
When Not to Use a DBMS?
Dept Of ISE,DSCE 28
Schemas, Instances, and Database State
• The description of a database is called the database schema, which
is specified during database design and is not expected to change
frequently.
• A displayed schema is called a schema diagram.
Dept Of ISE,DSCE 29
Schemas, Instances, and Database State
Dept Of ISE,DSCE 32
The Three-Schema Architecture
Dept Of ISE,DSCE 33
Data Independence
• Data independence is defined as the capacity to
change the schema at one level of a database
system without having to change the schema at
the next higher level.
• Two types of data independence are:
• Logical data independence is the capacity to
change the conceptual schema without having
to change external schemas or application
programs.
• Physical data independence is the capacity to
change the internal schema without having to
change the conceptual schema.
Dept Of ISE,DSCE 34
The Database System Environment
DBMS Component Modules
Dept Of ISE,DSCE 35
DBMS Component Modules
Dept Of ISE,DSCE 36
Database System Utilities
Dept Of ISE,DSCE 37
Tools, Application Environments, and
Communications Facilities
Dept Of ISE,DSCE 38