Scribd
Upload
2 views

02_Database_Environment

The document outlines the objectives and structure of the ANSI-SPARC three-level database architecture, emphasizing data independence and the roles of external, conceptual, and internal levels. It discusses the differences between Data Definition Language (DDL) and Data Manipulation Language (DML), as well as various data models used in database systems. Additionally, it highlights the functions of a Database Management System (DBMS) and the importance of a system catalog.

Uploaded by

isabellanuwagaba
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

02_Database_Environment

The document outlines the objectives and structure of the ANSI-SPARC three-level database architecture, emphasizing data independence and the roles of external, conceptual, and internal levels. It discusses the differences between Data Definition Language (DDL) and Data Manipulation Language (DML), as well as various data models used in database systems. Additionally, it highlights the functions of a Database Management System (DBMS) and the importance of a system catalog.

Uploaded by

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

Database

Management
systems
Lecturer 2:
Database Environment
(Adopted from Connoly&Begg: Database systems)

Mr. Kenneth Baguma


0782 285102
[email protected]
- Objectives
 Purpose of three-level database architecture.
 Contents of external, conceptual, and internal levels.
 Purpose
of external/conceptual and conceptual/internal
mappings.
 Meaning of logical and physical data independence.
 Distinction between DDL and DML.
A classification of data models.
 Purpose/importance of conceptual modeling.
 Typical functions and services a DBMS should
provide.
 Function and importance of system catalog.
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.
Objectives of Three-Level
Architecture
 DBA should be able to change database storage structures
without affecting the users’ views.

 Internalstructure 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
American National Standards- Institute (ANSI) Standards
Planning and Requirements Committee (SPARC),
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.
ANSI-SPARC Three-Level
Architecture
 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.
Data Independence
 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.
Data Independence and the ANSI-
SPARC Three-Level Architecture
Database Languages

 Data Definition Language (DDL)


 Allows the DBA or user to describe and name entities,
attributes, and relationships required for the application
 plus any associated integrity and security constraints.
Database Languages
 Data Manipulation Language (DML)
 Provides basic data manipulation operations on data held
in the database.
 insertion of new data into the database;
 modification of data stored in the database;
 retrieval of data contained in the database;
 deletion of data from the database.
 Procedural DML
 allows user to tell system exactly how to manipulate data.
 Non-Procedural DML
 allows user to state what data is needed rather than how
it is to be retrieved.
 Fourth Generation Languages (4GLs)
 Form generators, report generators, Graphics generators ,
Application generators
Data Model
Integrated collection of concepts for describing data,
relationships between data, and constraints on the data in
an organization.
 Data Model comprises:
 a structural part; consisting of a set of rules
according to which databases can be
constructed
 a manipulative part; defining the types of
operation that are allowed on the data
 a set of integrity rules, which ensures that the data
is accurate
Data Model
 Purpose
 To represent data in an understandable way. If it does
this, then it can be easily used to design a
database
 To reflect the ANSI-SPARC architecture, we can
identify three related data models:
 an external data model, to represent each user’s view
of the organization, sometimes called the Universe of
Discourse (UoD);
 a conceptual data model, to represent the logical (or
community) view that is DBMS-independent;
 an internal data model, to represent the conceptual
schema in such a way that it can be understood by
the DBMS.
Categories of Data Models
 Object-Based Data Models: - use concepts such as entities,
attributes, and relationships.
 Entity-Relationship
 Semantic
 Functional
 Object-Oriented.
 Record-Based Data Models: - the database consists of a
number of fixed-format records
 Relational Data Model
 Network Data Model
 Hierarchical Data Model.
 Physical Data Models: describe how data is stored in the
computer, representing information such as record structures, record
orderings, and access paths
Relational Data Model
Network Data Model
Hierarchical Data Model
Conceptual Modeling
 Conceptual schema is the core of a system supporting all
user views.
 Should be complete and accurate representation of an
organization’s data requirements.

 Conceptual modeling is process of developing a model of


information use that is independent of implementation
details.
 Result is a conceptual data model.
Functions of a DBMS
 Data Storage, Retrieval, and Update.
 A User-Accessible Catalog.
 Transaction Support.
 Concurrency Control Services.
 Recovery Services.
 Authorization services
 Support for data communication
 Integrity services
 Services to promote data independence
 Utility Services
System Catalog
 Repository of information (metadata) describing the data
in the database.
 One of the fundamental components of DBMS.
 Typically stores:
 names, types, and sizes of data items;
 constraints on the data;
 names of authorized users;
 data items accessible by a user and the type of access;
 usage statistics.
Any Questions???

You might also like