Scribd
Upload
30 views14 pages

Architecture Levels

Uploaded by

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

Architecture Levels

Uploaded by

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

DBMS LEVELS / SCHEMA

Three Level Model / Schema

 Also called ANSI/SPARC architecture


or three-schema architecture.
(American National Standards Institute)
 To describe the structure of a specific database system.
 To separate the user applications and physical database.
 The three schema architecture contains three-levels.
 It breaks the database down into three different categories.
3 LEVELS

 External Schema
 Conceptual Schema / Logical Schema
 Internal Schema
Objectives of the 3 schemas
To enable multiple users to access the same data with a
Main Objective personalized view
To separates the user's view from the physical structure

 Different users need different views of the same data.


 The approach in which a particular user needs to see
the data may change over time.
 The users of the database should not worry about the
physical implementation
 internal workings of the database such as data
compression and encryption techniques, hashing,
optimization of the internal structures etc.
 All users should be able to access the same data
according to their requirements.
 DBA should be able to change the conceptual
structure of the database without affecting the user's
Internal Level Schema
 Describes the physical storage
structure of the database.

 The internal schema is also known as a


physical schema.

 It uses the physical data model. It is used


to define that how the data will be stored
in a block.

 The physical level is used to describe


complex low-level data structures in
detail.
Concerns of Internal Schema

 Storage space allocations.


For Example: B-Trees, Hashing etc.

 Access paths.
For Example: Specification of primary and secondary keys,
indexes, pointers and sequencing.

 Data compression and encryption techniques.

 Optimization of internal structures.

 Representation of stored fields.


Conceptual Schema / Logical
Schema
 describes the design of a database at the conceptual level.
 describes the structure of the whole database.
 describes relationship exists among those data.
 Programmers and database administrators (DBA) work at this
level.
External Level
 An external schema is also known as view schema.

 At the external level, a database contains several schemas that sometimes called as
subschema.

 The subschema is used to describe the different view of the database.

 Each view schema describes the database part that a particular user group is
interested and hides the remaining database from that user group.

 Describes the end user interaction with database systems.


DBA
 Create and Issue usernames and passwords

 Set Access rights / privileges

 Create (regular / scheduled) backups

 Encryption of data

 Definition of different views

 Usage monitoring / logging of activity


DBA
Create and Issue usernames and passwords
 stops unauthorised access to the data

 any further expansion e.g. strong passwords / passwords should be changed


regularly etc…

Set Access rights / privileges


 so that only relevant staff / certain usernames can read/edit certain parts of
the data

 can be read only, or full access / read, write and delete

 any relevant example e.g. only class tutors can edit details of pupils in their
tutor group
DBA
Create (regular / scheduled) backups
 In case of loss/damage to the live data a copy is available

 e.g. backing up the data at the end of each day and storing the data off-site/to a

separate device

Encryption of data
 If there is unauthorized access to the data it cannot be understood, it should need a

decryption key

 e.g. Bank details of an account holder are encrypted before being sent over the
DBA
Definition of different views
 composed of one or more tables

 controls the scope of the data accessible to authorised users

 E.g Account holder and manager

Usage monitoring / logging of activity


 creation of an audit /activity log

 records the use of the data in the database / records operations performed by all users /
all access to the data

 example keeping track of record showing, who accessed the specific account
DATA DICTIONARY
 Stores all the information about the database
 data about the data
 metadata about the database

Example:
 table names
 data types
 field names
 Relationships
 Primary keys, foreign keys
 Validation rules

You might also like