PRESENTATION

NAME: BODANE MANDAR

ENROLLMENT NO: 72474

SUBJECT: Advance Database System

TOPIC: Multi DBMS Architecture

1
Introduction
 Architecture defines the structure of the system
 components identified
 functions of each component defined
 interrelationships and interactions between components
defined

2
Reference Model （参考模型）
 Reference Model
 A conceptual framework whose purpose is to divide
standardization work into manageable pieces and to
show at a general level how these pieces are related to
one another.
 Three approaches to define a reference model
① Component-based
– Components of the system are defined together with the
interrelationships between components
– Good for design and implementation of the system

3
Reference Model (cont.)
② Function-based
– Classes of users are identified together with the functionality
that the system will provide for each class
– The objectives of the system are clearly identified. But how do
you achieve these objectives?

③ Data-based
– Identify different types of data and specify the functional units
that will realize and/or use data according to these views.
– The ANSI/SPARC architecture discussed next belongs to this
category.

4
ANSI/SPARC Architecture

Users

External External External External

Schema View View View

Conceptual Conceptual
Schema View

Internal Internal
Schema View

5
The Top-Down Classical DDBMS
Architecture
Global Schema

Fragmentation Schema
Site Independent
Schemas
Allocation Schema

Local Mapping Schema Local Mapping Schema Other sites

DBMS 1 DBMS 2

Site 1 LOCA LOCA

L
Site 2 L
DB 1 DB 2 6
Outline
 Bottom-up Design of DDBMS Architecture

Three Reference Architectures for a DDBMS:

1.Client/server Architecture
2.Peer-to-Peer Architecture for distributed DBMS
3.Multi-databases Architecture

7
Bottom-up Architectural Models for
DDBMS
Possible ways in which multiple databases are put together for
sharing, which are characterized according to three dimensions.

Peer-to-peer
Distribution Distributed DBMS
Distributed
Multi-DBMS

Client/server

Multi-DBMS

Autonomy

Heterogeneity
Federated DBMS 8
Dimension 1: Distribution
 Whether the components of the system are located
on the same machine or not
 0 - no distribution - single site (D0)
 1 - client-server - distribution of DBMS functionality (D1)
 2 - full distribution - peer to peer distributed
architecture(D2)

9
Dimension 2: Heterogeneity
 Various levels (hardware, communication, operating
system)
 DBMS important ones (like data model, query
language, transaction management algorithms, etc.)
 0 - homogeneous (H0)
 1 - heterogeneous (H1)

10
Dimension 3: Autonomy
 Refers to the distribution of control, not of data,
indicating the degree to which individual DBMSs can
operate independently.
 Requirements of an autonomous system
 The local operations of the individual DBMSs are not
affected by their participation in the DDBS.
 The individual DBMS query processing and optimization
should not be affected by the execution of global queries
that access multiple databases.
 System consistency or operation should not be
compromised when individual DBMSs join or leave the
distributed database confederation.
11
Distributed Database Reference
Architecture
ES1 ES2 ESn External Schema

GCS Global Conceptual Schema

LCS1 LCS2 LCSn Local Conceptual Schema

LIS1 LIS2 LISn Local Internal Schema

It is logically integrated. Provides for the levels of transparency

12
Components of a Multi-DBMS
User
System Responses User Requests

User Multi-DBMS Layer User

User Transaction Transaction User

Interface Manager Manager Interface

Query Query
Scheduler Scheduler
Processor Processor

Query Recovery Recovery Query

Optimizer Manager Manager Optimizer

Runtime Sup. Runtime Sup.

Processor Processor

Database Database
13
Multi-DBMS Architecture with a
Global Conceptual Schema
ES1 ES2 ESn

LES11 LES1s GCS LESn1 LESnt

LCS1 LCSn

LIS1 LISn

•The GCS is generated by integrating LES's or LCS's

•The users of a local DBMS can maintain their autonomy
•Design of GCS is bottom-up 14
Multi-DBMS without Global
Conceptual Schema
Multidatabase ES1 ES2 ES3
Layer

Local Database LCS LCS2 LCS3

1
System Layer

LIS1 LIS2 LIS3

 Local database system layer consists of several DBMSs which

present to multidatabase layer part of their databases
 The shared database has either local conceptual schema or
external schema (Not shown in the figure)
 External views on one or more LCSs.
 Access to multiple databases through application programs 15
 Multi-DBMS without Global
Conceptual Schema (cont.)
 Multi-DBMS components architecture
 Existence of fully fledged local DBMSs
 Multi-DBMS is a layer on top of individual DBMSs that
support access to different databases
 The complexity of the layer depends on existence of
GCS and heterogeneity
 Federated Database Systems
 Do not use global conceptual schema
 Each local DBMS defines export schema
 Global database is a union of export schemas
 Each application accesses global database through
import schema (external view) 16
Question & Answer

17