Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
52 views

Dbms

The document discusses the stages of information systems from manual to database management systems. It describes the components and advantages of database management systems including data independence, integrity, and administration. Key terms discussed include the three-level ANSI-SPARC architecture, conceptual, internal and external views, and mapping between the levels.

Uploaded by

Vaishali Ravi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
52 views

Dbms

The document discusses the stages of information systems from manual to database management systems. It describes the components and advantages of database management systems including data independence, integrity, and administration. Key terms discussed include the three-level ANSI-SPARC architecture, conceptual, internal and external views, and mapping between the levels.

Uploaded by

Vaishali Ravi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 25

INTRODUCTION TO DATABASE

STAGES OF INFORMATION SYSTEM

 Stage 0: Manual Information System


 Records
 Files
 Index Cards
 Stage 1: Sequential Information Systems
 Tapes
 Files
 slow, non-interactive, redundancy,...
 Stage 2: File Based Information Systems
 Disk (direct access)
 application program has its own file data dependence
 data redundancy
 Stage 3: DBMS based Information Systems
 Generalized data management software
 Transaction processing
DATABASE MANAGEMENT SYSTEM

 Collection of interrelated data


 Set of programs to access the data
 DBMS contains information about a particular enterprise
 DBMS provides an environment that is both convenient and efficient to use.
 A database management system (DBMS) refers to the technology for creating and
managing databases. Basically, DBMS is a software tool to organize (create, retrieve,
update and manage) data in a database.
 The main aim of a DBMS is to supply a way to store up and retrieve database
information that is both convenient and efficient.
DISADVANTAGES OF FILE PROCESSING SYSTEM
 Data redundancy and Inconsistency
 Some information may be duplicated in several files, for example, the address and telephone
number of a particular customer may appear in a file that consists of saving account records and in
a file that consists of checking account records. This redundancy leads higher storage and access
cost.
 In addition, it may lead to data inconsistency, for example a change in customer address may be
reflected in saving account records but not elsewhere in the system
 Difficulty in accessing data
 File processing environments do not allow needed data to be retrieved in a convenient and efficient
manner.
 Data isolation
 Because data are scattered in various files and file may be in different formats, it is difficult to write
new application programs to retrieve the appropriate data.
 Integrity problems
 The data values stored in the database must satisfy certain times of consistency constraints.
Developers enforce these constraints in the system by adding appropriate code in the various
application programs.
 However, when new constraints are added, it is difficult to change to enforce them; the problem is
compounded when the constraint involves several data items from different files.
 Concurrent access anomalies
 Data in a system may be accessed by many different application programs that have not been
coordinated previously, however supervision is difficult to provide.
 Security problems
 Not every user use the database system should be able to access all the data. It is difficult to
enforce such security constraints.
WHY USE DBMS?

 To develop software applications In less time.


 Data independence and efficient use of data.
 For uniform data administration.
 For data integrity and security.
 For concurrent access to data, and data recovery from crashes.
 To use user-friendly declarative query language.
WHERE DBMS IS USED?

 Airlines: reservations, schedules etc


 Telecom: calls made, customer details, network usage etc
 Universities: registration, results, grades etc
 Sales: products, purchases, customers etc
 Banking: all transactions etc
ADVANTAGES OF DBMS

 Data independence:
 Application programs should be as free or independent as possible from details of data representation and
storage. DBMS can supply an abstract view of the data for insulating application code from such facts.
 Efficient data access:
 DBMS utilizes a mixture of sophisticated concepts and techniques for storing and retrieving data competently
and this feature becomes important in cases where the data is stored on external storage devices.
 Data integrity and security:
 If data is accessed through the DBMS, the DBMS can enforce integrity constraints on the data.

 Data administration:
 When several users share the data, integrating the administration of data can offer major improvements.
 Experienced professionals understand the nature of the data being managed and can be responsible for
organizing the data representation to reduce redundancy and make the data to retrieve efficiently.
COMPONENTS OF DBMS
 Users: Users may be of any kind such as DB administrator, System developer or
database users.
 Database application: Database application may be Departmental, Personal,
organization's and / or Internal.
 DBMS: Software that allows users to create and manipulate database access,
 Database: Collection of logical data as a single unit.
DISADVANTAGES OF DBMS

 A significant Disadvantage of the DBMS is cost. The DBMS and the additional
hardware which is needed to support it can be expensive.
 Integrating a new DBMS into an existing system cause problems, particularly if the
DBMS is incompatible with any other DBMS already with the organisation.
 A DBMS is a complex piece of software and is likely to be more vulnerable to failure
than a file processing system. Recovery from failure may be more difficult. Although a
good DBMS should have sound recovery procedures.
 One of the major aims of a database is to supply users with an abstract view of data,
hiding a certain element of how data is stored and manipulated.
 So, the starting point for the design of a database must be an abstract and general
description of the information requirements of the organization that is to be
represented in the database.
 And hence you will require an environment to store data and make it work like a
database.
DATABASE ENVIRONMENT

 A database environment is a collective system of components that comprise and regulates the
group of data, management, and use of data which consist of software, hardware, people,
techniques of handling database and the data also.
 the hardware in a database environment means the computers and computer peripherals that
are being used to manage a database
 the software means the whole thing right from the operating system (OS) to the application
programs that includes database management software like M.S.Access or SQL Server
 the people in a database environment include those people who administrate and use the system
 The techniques are the rules, concepts, and instructions given to both the people and the
software along with the data with the group of facts and information positioned within the
database environment.
THE THREE LEVEL ANSI-SPARC ARCHITECTURE
 External Level:
 Defined by user or application programmer in consultation by DBA.

 Conceptual Level:
 Defined by DBA.

 Internal Level:
 Defined by DBA for an optimisation.
 External View
 These are local views of the database which are also known as external views, user views or
application views
 concern to a user or application program are included
 As an illustration from the student record keeping system, we can define two distinct applications,
the examination branch application and the student welfare application.
 The examination branch application and the student welfare application will need to access
different portions of the database.
 The two functions, what part of the database is shown to the user and how it is shown are major
components of an external view.
 Conceptual View
 all the database entities and its relationships among them are included.
 represents the entire database.
 defines all the data to be stored in the database, the constraints which apply to the data, in what
format data is to be held and which data item are to be grouped together
 Internal View
 A description of the actual method of storing data
 indicates how the data will be stored and describes the data structures and access methods to be
used by the database
 contains the definition of the stored record, the method of representing the data field and the
access aids used
 only the internal view representing the total database as it is actually stored
MAPPING IN THE ARCHITECTURE

 The definitions of three types of view are independent of each other.


 mapping describes the correspondence between one type of view and another.
 Mapping between the external schema and the internal schema is done in two steps
via the conceptual schema.
 External/Conceptual Mapping
 This mapping is between an external schema and the conceptual schema. This describes how a
particular schema is derived from the conceptual schema
 Conceptual/Internal Mapping
 This mapping is between conceptual schema and internal schema. This specifies how data described
at conceptual schema are represented at the internal level, the method of deriving the conceptual
record from the physical database.
DATA INDEPENDANCE

 A major objective for the three-level architecture is to provide data independence,


which means that upper levels are unaffected by changes to lower levels
 Logical Data Independence (LDI)
 the immunity of the external schemas to changes in the conceptual schema.
 If the conceptual schema or the logical description of the data changes, it is possible to derive the
earlier description of data from the new description by changing the external/conceptual mapping
 Example:
 Suppose the student record was initially described in the conceptual schema as,
STUDENT (reg_no, name, address, age)
 conceptual schema is to be changed and the date_of_birth is to replace age. Even though the conceptual
schema is changed to record date of birth, it is possible to derive the age of a given student by changing the
external/conceptual mapping to calculate the age using date of birth and current date.
 Suppose we need to add a new field in the student record such as medium of study. This will change the
definition of the student record in the conceptual schema, but no changes are needed in any of the external
schemata which do not contain any references to the new field.
 Physical Data Independence (PDI)
 the physical storage structures or devices used for storing the data could be
changed without necessitating a change in the conceptual view or any of the
external views.
 The change would be absorbed by the mapping between the conceptual and
internal level.

You might also like