Scribd
Upload
38 views

Introduction of DB: Database System Concepts and Architecture

The document discusses database concepts including data models, schemas, and the three-level ANSI-SPARC architecture. It describes conceptual, physical, and implementation data models and distinguishes between database schemas and instances. It explains the objectives of the three-level architecture in providing logical and physical data independence and multiple views of data. Finally, it briefly introduces client-server architectures.

Uploaded by

Zahid Ahmad
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
38 views

Introduction of DB: Database System Concepts and Architecture

The document discusses database concepts including data models, schemas, and the three-level ANSI-SPARC architecture. It describes conceptual, physical, and implementation data models and distinguishes between database schemas and instances. It explains the objectives of the three-level architecture in providing logical and physical data independence and multiple views of data. Finally, it briefly introduces client-server architectures.

Uploaded by

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

Introduction of DB

Database System
Concepts and
Architecture
Data Models
 Data Model: A set of concepts to describe
the structure of a database, and certain
constraints that the database should obey.
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.
 Implementation (representational) data models:
Provide concepts that fall between the above two,
balancing user views with some computer storage
details.
Schemas versus Instances
• Database Schema: The description of a database.
Includes descriptions of the database structure and
the constraints that should hold on the database.
• Schema Diagram: A diagrammatic display of
(some aspects of) a database schema.
• Database Instance: The actual data stored in a
database at a particular moment in time. Also
called database state (or occurrence).
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 when it is
loaded
• Valid State: A state that satisfies the structure and
constraints of the database.
• Distinction
• The database schema changes very infrequently. The database
state changes every time the database is updated.
• Schema is also called intension, whereas state is called
extension.
Three-level Architecture
 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.
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.

 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.
Three-Schema Architecture
• Proposed to support DBMS characteristics
of:
• Program-data independence.
• Support of multiple views of the data.
Three-Schema Architecture
• Defines DBMS schemas at three levels:
• Internal schema at the internal level to describe
physical storage structures and access paths. 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 level.
• Presentation layer.
• Different for different users i.e. Students, teacher.
• Different for different platforms i.e. tablet, pc, mobile
Three-Schema Architecture
External schema
•evolves as user needs are modified over time.
•DBMS uses external views to create user interfaces
(Data entry Forms) for different users which is both the
facility and barrier.
•Users may have different views of the same data e.g.
date, time etc.
•Each user has a view of the database limited to the
appropriate portion of the user’s perspective of reality.
•In External Level Virtual/calculated data: that is not
actually stored in the database but is created when
needed e.g. age, Averages, or other statistical data etc.
Three-Schema Architecture
Conceptual schema
•The entire information structure of the database,
as seen by the DBA.
•The community view of data
•Communicate with External Schema to get data
•Clients need to communicate with this layer to
get to DB.
•Perform operation i.e. credit card transection.
•Contains Semantic information about the data
meaning, security and integrity rules.
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.
ANSI-SPARC Three-Level
Architecture
Employee Data Workers
Aisha
First Name: Rana Name: R. Aslam
Last Name: Aslam Age: 33y
Date of Birth: Dept: Sales
12 Sep, 1985
Saleem
External Layer
Logical Recor d Interface
Conceptual Layer

Name DoB Grade DepId


Rana Aslam 12/09/85 17 D001
Marya Wasti 29/02/86 18 D005
Differences between Three Levels of
ANSI-SPARC Architecture
Data Independence
• Logical Data Independence: The capacity
to change the conceptual schema without
having to change the external schemas and
their application programs.
• Physical Data Independence: The capacity
to change the internal schema without
having to change the conceptual schema.
Data Independence
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.
Data Independence and the
ANSI-SPARC Three-Level
Architecture
DBMS Server
• Provides database query and transaction
services to the clients
• Sometimes called query and transaction
servers
Two Tier Client-Server
Architecture
• User Interface Programs and Application
Programs run on the client side
• Interface called ODBC (Open Database
Connectivity – s) provides an Application
program interface (API) allow client side
programs to call the DBMS. Most DBMS
vendors provide ODBC drivers.
Two Tier Client-Server
Architecture
• A client program may connect to several DBMSs.
• Other variations of clients are possible: e.g., in
some DBMSs, more functionality is transferred to
clients including data dictionary functions,
optimization and recovery across multiple servers,
etc. In such situations the server may be called the
Data Server.
Three Tier Client-Server
Architecture
• Common for Web applications
• Intermediate Layer called Application Server or
Web Server:
• stores the web connectivity software and the rules and
business logic (constraints) part of the application used to
access the right amount of data from the database server
• acts like a conduit for sending partially processed data
between the database server and the client.
• Additional Features- Security:
• encrypt the data at the server before transmission
• decrypt data at the client

You might also like