Design and Architc - Lect 7 - 1

DISTRIBUTED DBMS
ARCHITECTURE-1
Reference Book : Principles of Distributed Database Systems
EDITION THIRD
Author: M. Tamer Ozsu
Course:DDB
Instructor: Ibrar Afzal
Hazara University Mansehra, IT Department
DBMS STANDARDIZATION
• Based on components.
The components of the system are defined together with the
interrelationships between components. A DBMS consists of a number
of components, each of which provides some functionality.
• Based on functions.
The different classes of users are identified and the functions that the
system will perform for each class are defined. The system
specifications within this category typically specify a hierarchical
structure for the user classes.
2
• Based on data.
The different types of data are identified, and an architectural
framework is specified which defines the functional units that will
realize or use data according to these different views. This approach
(also referred as the datalogical approach) is claimed to be the
preferable choice for standardization activities.
3
ANSI / SPARC ARCHITECTURE
The ANSI / SPARC architecture is claimed to be based on

the data organization. It recognizes three views of data:
the external view, which is that of the user, who might be a
programmer; the internal view, that of the system or
machine; and the conceptual view, that of the enterprise.
For each of these views, an appropriate schema definition

is required.
4
5
• At the lowest level of the architecture is the internal view,
which deals with the physical definition and organization
of data.
• At the other extreme is the external view, which is

concerned with how users view the database.
• Between these two ends is the conceptual schema, which

is an abstract definition of the database. It is the „real
world” view of the enterprise being modeled in the
database.
6
7
• The square boxes represent processing functions, whereas the

hexagons are administrative roles.
• The arrows indicate data, command, program, and description flow,
whereas the „I”-shaped bars on them represent interfaces.
• The major component that permits mapping between different data
organizational views is the data dictionary / directory (depicted as a
triangle), which is a meta-database.
8
• The database administrator is responsible for defining the internal

schema definition.
• The enterprise administrator’s role is to prepare the conceptual
schema definition.
• The application administrator is responsible for preparing the external
schema for applications.
9
A Generic Centralized DBMS Architecture
DBMS is interfaced with two other components to run a PC:
• Communication subsystem
 To communicate with applications interface is permitted e.g;
• Running interactive transactions
• Operating system provides interface between

 DBMS and computer resources (processor, memory, disk drives, etc.)
10
Functions are performed through layers in top down approach:
• Interface
• Control
• Compilation
• Execution
• Data access
• Consistency management.
11
Fig: Functional Layers of Centralized DBMS

12
Functional Layers of Centralized DBMS
The interface layer
• Manages the interface to the applications like
 SQL embedded in a host language in the case of relational DBMSs
 C and QBE (Query-by-Example).
• Database application programs are executed against external views
 A view is a relation derived from base relations as the result of a relational query
 Views are useful for ensuring data security by hiding some data and restrict access
 A view is useful in representing its particular perception of the database
 A view in relational DBMSs is a virtual relation derived from base relations by
applying relational algebra operation
 View management consists of translating the user query from external data to
conceptual data.
13
The Control layer
• “Authorized users perform correct operations on the database”
• A predicate is the condition that must be met for the user to be able to
access the requested source.
• Controls the query by adding semantic integrity predicates
 Semantic integrity ensures that data entered into a row reflects an allowable value
for that row. The value must be within the domain.
 Semantic integrity control ensures
 Database consistency by rejecting update transactions that lead to inconsistent database
states, or by activating specific actions on the database state i.e. updated database must
satisfy the set of integrity constraints
• Enforcing integrity constraints is costly because it generally requires access to a large
amount of data that are not directly involved in the database updates
14
The Control layer Continues…
• Authorization predicates.
 Authorized users perform correct operations on the database,
contributing to the maintenance of database integrity.
 database administrator (DBA).
• The output of this layer is an enriched query in the high-level language
accepted by the interface.
15
Query processing (or compilation) layer
 Maps the query into an optimized sequence of lower-level operations.

 This layer is concerned with performance.
 It decomposes the query into a tree of algebra operations
 Find the “optimal” ordering of the operations.
 The result is stored in an access plan.
The output of this layer is

 Query expressed in lower-level code (algebra operations).
16
Execution layer
– Directs the execution of the access plans
• Transaction management(commit, restart) and synchronization of algebra operations.
– It interprets the relational operations
• Calling the data access layer through the retrieval and update requests.
The data access layer

– Manages the data structures that implement the ﬁles, indices, etc.
– It also manages the buffers by caching the most frequently accessed data.
– It minimizes the access to disks to get or write data.
Consistency layer
– Manages concurrency control and logging for update requests.
– This layer allows transaction, system, and media recovery after failure.
17
Thanks
18

Design and Architc - Lect 7 - 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Design and Architc - Lect 7 - 1

Uploaded by

Copyright:

Available Formats

DISTRIBUTED DBMS

The ANSI / SPARC architecture is claimed to be based on

For each of these views, an appropriate schema definition

• At the other extreme is the external view, which is

• Between these two ends is the conceptual schema, which

• The square boxes represent processing functions, whereas the

• The database administrator is responsible for defining the internal

• Operating system provides interface between

Fig: Functional Layers of Centralized DBMS

 Maps the query into an optimized sequence of lower-level operations.

The output of this layer is

The data access layer

You might also like