Scribd
Upload
3 views

Database Environment

The document outlines the objectives and structure of the ANSI-SPARC three-level architecture for databases, which includes external, conceptual, and internal levels to ensure data independence and user-specific views. It also discusses various database languages, data models, and the functions of a Database Management System (DBMS). Additionally, it highlights the components of a DBMS and the advantages of client-server architectures.

Uploaded by

abyss1993.xy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

Database Environment

The document outlines the objectives and structure of the ANSI-SPARC three-level architecture for databases, which includes external, conceptual, and internal levels to ensure data independence and user-specific views. It also discusses various database languages, data models, and the functions of a Database Management System (DBMS). Additionally, it highlights the components of a DBMS and the advantages of client-server architectures.

Uploaded by

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

DATABASE

ENVIRONMENT

2
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.

5
Objectives of Three-Level Architecture
• 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.

6
ANSI-SPARC Three-level Architecture

7
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.

8
ANSI-SPARC Three-level Architecture

• Internal Level
• Physical representation of the database on the computer.
• Describes how the data is stored in the database.

9
Differences between Three Levels of ANSI-
SPARC Architecture

10
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.

14
Database Languages
• Data Manipulation Language (DML)
• Provides basic data manipulation operations on data held in 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.

15
Database Languages
• Fourth Generation Language (4GL)
• Query Languages
• Forms Generators
• Report Generators
• Graphics Generators
• Application Generators

16
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
• A manipulative part
• Possibly a set of integrity rules

17
Data Model
• Purpose
• To represent data in an understandable way.

• Categories of data models include:


• Object-based
• Record-based
• Physical

18
Data Models
• 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

19
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.

20
Functions of a DBMS
• Data Storage, Retrieval, and Update.

• A User-Accessible Catalog.

• Transaction Support.

• Concurrency Control Services.

• Recovery Services.

21
Functions of a DBMS
• Authorization Services.

• Support for Data Communication.

• Integrity Services.

• Services to Promote Data Independence.

• Utility Services.

22
Components of a DBMS

23
Components of Database Manager (DM)

24
Multi-User DBMS Architectures
• Teleprocessing

• File-server

• Client-server

25
Client-server
• Server holds the database and the DBMS.
• Client manages user interface and runs applications.
• Advantages include:
• wider access to existing databases
• increased performance
• possible reduction in hardware costs
• reduction in communication costs
• increased consistency.

26
Client-server Architecture

27
System Catalog
• Repository of information (metadata) describing the data in the
database.
• Typically stores:
• Names of authorized users.
• Names of data items in the database.
• Constraints on each data item.
• Data items accessible by a user and the type of access.
• Used by modules such as Authorization Control and Integrity
Checker.

28

You might also like