Scribd
Upload
60 views15 pages

Fundamentals of Databases

The document discusses fundamentals of database management systems including basic definitions of databases, data, and DBMS; main characteristics of the database approach such as self-describing nature, insulation between programs and data, data abstraction, and supporting multiple views; and historical development of database technology from hierarchical and network models to relational and object-oriented models.

Uploaded by

nagaaytha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
60 views15 pages

Fundamentals of Databases

The document discusses fundamentals of database management systems including basic definitions of databases, data, and DBMS; main characteristics of the database approach such as self-describing nature, insulation between programs and data, data abstraction, and supporting multiple views; and historical development of database technology from hierarchical and network models to relational and object-oriented models.

Uploaded by

nagaaytha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

Fundamentals of

Database Management
Systems

The goal of all inanimate objects is to resist


man and ultimately to defeat him
By Russell Baker, 1968
Basic Definition
Database: A collection of related data.
Data: Known facts that can be recorded and have an implicit
meaning.
Mini-world: Some part of the real world about which data is
stored in a database. For example, student grades and
transcripts at a university.
Database Management System (DBMS): A software
package/ system to facilitate the creation and maintenance
of a computerized database.
Database System: The DBMS software together with the data
itself. Sometimes, the applications are also included.
Main Characteristics of the
Database Approach
Self-describing nature of a database system: A
DBMS catalog stores the description of the
database. The description is called meta-data).
This allows the DBMS software to work with
different databases.

Insulation between programs and data: Called


program-data independence. Allows
changing data storage structures and operations
without having to change the DBMS access
programs.
Main Characteristics of the
Database Approach
Data Abstraction: A data model is used to hide storage
details and present the users with a conceptual view of the
database.

Support of multiple views of the data: Each user may see a


different view of the database, which describes only the data of
interest to that user.

Sharing of data and multiuser transaction processing :


allowing a set of concurrent users to retrieve and to update the
database. Concurrency control within the DBMS guarantees that
each Transaction is correctly executed or completely aborted.
OLTP (Online Transaction Processing) is a major part of
database applications.
Database Users
Database administrators: responsible for authorizing access to the database,
for coordinating and monitoring its use, acquiring software, and hardware
resources, controlling its use and monitoring efficiency of operations.

Database Designers: responsible to define the content, the structure, the


constraints, and functions or transactions against the database. They must
communicate with the end-users and understand their needs.

End-users: they use the data for queries, reports and some of them actually
update the database

Casual : access database occasionally when needed

Parametric : they make up a large section of the end-user population. They use
previously well-defined functions in the form of canned transactions against the
database. Examples are bank-tellers or reservation clerks who do this activity for
an entire shift of operations.
Historical Development of
Database Technology
Early Database Applications: The Hierarchical and Network
Models were introduced in mid 1960s and dominated during the
seventies. A bulk of the worldwide database processing still occurs using
these models.

Relational Model based Systems: The model that was originally


introduced in 1970 was heavily researched and experimented with in
IBM and the universities. Relational DBMS Products emerged in the
1980s.

Object-oriented applications: OODBMSs were introduced in late


1980s and early 1990s to cater to the need of complex data processing
in CAD and other applications. Their use has not taken off much.

Data on the Web and E-commerce Applications: Web contains


data in HTML (Hypertext markup language) with links among pages.
This has given rise to a new set of applications and E-commerce is using
new standards like XML (eXtended Markup Language).
Objectives of Three-Level
Architecture
All users should be able to access same data.

A user's view is immune to changes made in other


views.

Users should not need to know physical database


storage details.

DBA should be able to change database storage


structures without affecting the users' views.

Internal structure of database should be unaffected


by changes to physical aspects of storage.

DBA should be able to change conceptual structure of


database without affecting all users.
ANSI-SPARC Three-level
Architecture
ANSI-SPARC Three-level
Architecture
External Level
Users' view of the database. Describes
that part of database that is relevant to a
particular user.

Conceptual Level
Community view of the database.
Describes what data is stored in database
and relationships among the data.
Internal Level
Physical representation of the database
on the computer. Describes how the data
is stored in the database.
Differences between
Three Levels of ANSI-
SPARC Architecture
Data Independence
Logical Data Independence
Refers to immunity of external schemas to
changes in conceptual schema.
Conceptual schema changes e.g. addition/removal
of entities.
Should not require changes to external schema or
rewrites of application programs.

Physical Data Independence


Refers to immunity of conceptual schema to
changes in the internal schema.
Internal schema changes e.g. using different file
organizations, storage structures/devices.
Should not require change to conceptual or
external schemas.
DataIndependenceandtheANSI
SPARCThreelevelArchitecture
Data Model
Collection of concepts for describing data,
relationships between data and constraints on
the data in an organization.

Data Model comprises:


A structural part
A manipulative part
Possibly a set of integrity rules

Purpose
To represent the data in an understandable way.

Categories of data models include:


Object-based
Record-based
Physical
Data Model
Object-based Data Models
Entity-Relationship
Semantic
Functional
Object-Oriented

Record-based Data Models


Relational Data Model
Network Data Model
Hierarchical Data Model

Physical Data Models


ER (Entity Relationship) Model
Entity - the main object in the problem
domain.
Attribute - describes the main object
(entity).
Relation - association defines the
between entity.

You might also like