Scribd
Upload
18 views

Databases: Chapter 2: Database System Concepts and Architecture

This document provides an overview of database system concepts and architecture. It defines key terms like data models, schemas, and instances. It describes common data model categories and features like constraints and operations. It also explains the three-schema database architecture including the internal, conceptual, and external schemas. The document outlines common DBMS components, languages, interfaces and utilities as well as classifications of database systems.

Uploaded by

Muhammad Arif Azim
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
18 views

Databases: Chapter 2: Database System Concepts and Architecture

This document provides an overview of database system concepts and architecture. It defines key terms like data models, schemas, and instances. It describes common data model categories and features like constraints and operations. It also explains the three-schema database architecture including the internal, conceptual, and external schemas. The document outlines common DBMS components, languages, interfaces and utilities as well as classifications of database systems.

Uploaded by

Muhammad Arif Azim
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 29

DATABASES

Fall 2016

Chapter 2 : Database
System Concepts and
Architecture

Ref 2.1 Data Models


Data Model:
A set of concepts to describe the structure of a
database, the operations for manipulating these
structures, and certain constraints that the database
should obey.

Data Model Structure and Constraints:


Constructs are used to define the database structure
Constructs typically include elements (and their data
types) as well as groups of elements (e.g. entity,
record, table), and relationships among such groups
Constraints specify some restrictions on valid data;
these constraints must be enforced at all times

Data Models (continued)


Data Model Operations:
These operations are used for specifying
database retrievals and updates by
referring to the constructs of the data
model.
Operations on the data model may
include basic model operations (e.g.
generic insert, delete, update) and userdefined operations (e.g.
compute_student_gpa, update_inventory)

Categories of Data Models


Conceptual (high-level, semantic) data models:
Provide concepts that are close to the way many users
perceive data.
(Also called entity-based or object-based data models.)

Physical (low-level, internal) data models:


Provide concepts that describe details of how data is
stored in the computer. These are usually specified in an
ad-hoc manner through DBMS design and administration
manuals

Implementation (representational) data models:


Provide concepts that fall between the above two, used by
many commercial DBMS implementations (e.g. relational
data models used in many commercial systems).

Entity-Relationship Model
Example of schema in the entityrelationship model

Relational Data Model


A Sample Relational Database

Schemas versus Instances


Database Schema:
The description of a database.
Includes descriptions of the database
structure, data types, and the constraints on
the database.

Schema Diagram:
An illustrative display of (most aspects of) a
database schema.

Schema Construct:
A component of the schema or an object
within the schema, e.g., STUDENT, COURSE.

Schemas versus Instances


Database State:
The actual data stored in a database at
a particular moment in time. This
includes the collection of all the data in
the database.
Also called database instance (or
occurrence or snapshot).
The term instance is also applied to
individual database components, e.g. record
instance, table instance, entity instance

Database Schema
vs. Database State
Database State:
Refers to the content of a database at a
moment in time.

Initial Database State:


Refers to the database state when it is
initially loaded into the system.

Valid State:
A state that satisfies the structure and
constraints of the database.

Database Schema
vs. Database State
(continued)

Distinction

The database schema changes very


infrequently.
The database state changes every
time the database is updated.

Schema is also called intension.


State is also called extension.

Example of a Database
Schema

Example of a database state

Ref 2.2 :Three-Schema


Architecture
Proposed by ANSI/SPARC to support
DBMS characteristics of:
Program-data independence.
Support of multiple views of the data.

Not explicitly used in commercial


DBMS products, but has been useful
in explaining database system
organization

Three-Schema Architecture
(Cont.)

Defines DBMS schemas at three levels:


Internal schema at the internal level to describe
physical storage structures and access paths (e.g
indexes).
Typically uses a physical data model.

Conceptual schema at the conceptual level to describe


the structure and constraints for the whole database for
a community of users.
Uses a conceptual or an implementation data model.

External schemas at the external level to describe the


various user views.
Usually uses the same data model as the conceptual
schema.

Three-Schema Architecture
Mappings among schema levels are
needed to transform requests and data.
Programs refer to an external schema, and
are mapped by the DBMS to the internal
schema for execution.
Data extracted from the internal DBMS
level is reformatted to match the users
external view (e.g. formatting the results of
an SQL query for display in a Web page)

Data Independence
Logical Data Independence:
The capacity to change the conceptual schema
without having to change the external schemas
and their associated application programs.

Physical Data Independence:


The capacity to change the internal schema
without having to change the conceptual
schema.
For example, the internal schema may be
changed when certain file structures are
reorganized or new indexes are created to
improve database performance

Data Independence
(continued)
When a schema at a lower level is
changed, only the mappings between
this schema and higher-level schemas
need to be changed in a DBMS that fully
supports data independence.
The higher-level schemas themselves are
unchanged.
Hence, the application programs need not be
changed since they refer to the external
schemas.

Ref2.3 DBMS Languages


Data Definition Language (DDL): Used by the
DBA and database designers to specify the
conceptual schema of a database. In many
DBMSs, the DDL is also used to define internal
and external schemas (views). In some DBMSs,
separate storage definition language (SDL)
and view definition language (VDL) are used
to define internal and external schemas.

DBMS Languages
(Cont.)
Data Manipulation Language (DML): Used to
specify database retrievals and updates.
- DML commands (data sublanguage) can be
embedded in a general-purpose programming
language (host language), such as COBOL,
PL/1 or PASCAL.
- Alternatively, stand-alone DML commands can
be applied directly (query language).

DBMS Interfaces
- Stand-alone query language interfaces.
- Programmer interfaces for embedding DML in
programming languages:
- Pre-compiler Approach
- Procedure (Subroutine) Call Approach

- User-friendly interfaces:

- Menu-based
- Graphics-based (Point and Click, Drag and Drop etc.)
- Forms-based
- Natural language
- Combinations of the above
- Speech as Input and Output
- Web Browser as an interface

DBMS Interfaces
(Cont.)
- Parametric interfaces using function keys.
- Report generation languages.
- Interfaces for the DBA:
- Creating accounts, granting authorizations
- Setting system parameters
- Changing schemas or access path

Ref 2.4.1: Typical DBMS


Component modules

Data Dictionary is metadata repository

Database System Utilities


To perform certain functions such as:
- Loading data stored in files into a
database.
- Backing up the database periodically on
tape.
- Reorganizing database file structures.
- Report generation utilities.
- Performance monitoring utilities.
- Other functions, such as sorting , user
monitoring , data compression , etc.

Ref2.6 Classification of
DBMSs
(Cont.)

Based on the data model used:


- Traditional: Relational, Network,
Hierarchical.
- Emerging: Object-oriented, Objectrelational.

Classification of DBMSs
(Cont.)
Other classifications:
- Single-user (typically used with microcomputers) vs. multi-user (most
DBMSs).
- Centralized (uses a single computer
with one database) vs. distributed (uses
multiple computers, multiple databases)

Classification of DBMSs
(Cont.)

Distributed Database Systems


have now come to be known as
client server based database
systems because they do not
support a totally distributed
environment, but rather a set of
database servers supporting a
set of clients.

You might also like