Scribd
Upload
47 views8 pages

Part 2

This document discusses distributed database management systems. It describes homogeneous and heterogeneous DBMS, as well as multi database systems. A homogeneous DBMS has all sites using the same DBMS product, while a heterogeneous one has sites using different DBMS products. A multi database system maintains autonomy at each site while allowing sharing of data. The document also outlines the functions of a distributed DBMS and describes the reference architecture, including global external schema, global conceptual schema, and local DBMS components.

Uploaded by

Mariane Calospo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
47 views8 pages

Part 2

This document discusses distributed database management systems. It describes homogeneous and heterogeneous DBMS, as well as multi database systems. A homogeneous DBMS has all sites using the same DBMS product, while a heterogeneous one has sites using different DBMS products. A multi database system maintains autonomy at each site while allowing sharing of data. The document also outlines the functions of a distributed DBMS and describes the reference architecture, including global external schema, global conceptual schema, and local DBMS components.

Uploaded by

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

LECTURE 8 DISTRIBUTED DATABASE MANAGEMENT SYSTEMS DDBMS PART 2

Learning Objectives

 Describe type of homogeneous and heterogeneous the DBMS and the multi database system
(MDBS)
 Explain functions and reference architecture of DBMS, MDBS and components of the DBMS
architecture

The DBMS may be classified Homogeneous DBMS as homogeneous or heterogeneous.

In a homogeneous system all sides use the same DBMS product. It is much easier to design and manage.
This approach provides incremental growth making the addition of a new site to the D DBMS easy and
allows increased performance by exploiting a parallel processing capability of multiple sites.

In a heterogeneous system sites may run different DBMS products which need not be based on the
same underlying data model. Heterogeneous system usually occur when individual sites have
implemented their own database and integration is considered at a later stage. In heterogeneous
system data may be required from another site that may have different hardware or different DBMS
products or different Hardware and different DBMS products.

Multi Database System DBMS


It is a DBMS in which each side maintains complete autonomy. It is logically integrate a number of
independently DBMS while allowing the local DBMS to maintain complete control of their operations. In
simpler terms it is a DBMS that resize transparently on top of existing database and file system and
presents a single database to is user. It allows users to access and share data without requiring physical
database integration. They are unfederated and federated MDBSS. Unfederated that means there are
no local users. A federated system is a cross between a distributed DBMS and a centralized DBMS. It is a
distributed system for global users and a centralized system for local users.

DDMS is expected to have all the functions of DBMS with additional functions:

 Extended communication services (to provide access to remote sites and allow the transfer of
queries and data among the sites using a network)
 Extended system catalog (to store data distribution details)
 Distribute query processing (including query optimization and remote data access)
 Extended security control to maintain appropriate authorization or access privileges to the
distributed data
 Extended concurrency control to maintain consistency of distributed and possibly replicate the
data
 Extended recovery services to take account of failures of individual sites and the failures of
communication links

Reference architecture for the DBMS due

Due diversity no accepted architecture equivalent to ANSI/SPARC 3-level architecture however a


reference architecture consists of:

 Set of global external schema


 Global conceptual schema (GCS )
 Fragmentation schema and allocation schema
 Set of schemas for each local DBMS conforming to 3 level ANSI/SPARC

The reference architecture diagram


For global external schema

It is for end-users who has the access to multiple size of database to get data in the system.

For global conceptual schema

It is a logical description of the whole database as if it were not distributed. This level
correspond to the conceptual level of ANSI/SPARC architecture and contains definition of entities,
relationships, constraints, security, and integrity information

For fragmentation schema

It is a description of how the data is to be logically partition. It is a union of our local


conceptual schemas in the system.

For allocation schema

It is description of where the data is to be located.

Each local DBMS has its own set of schemas. The local conceptual and local internet schemas
correspond to the equivalent levels of the ANSI/SPARC architecture. The local mapping schemas
maps fragment(?) In the allocation schema into external objects in the local database. It is DBMS
independent and is the basis for supporting heterogeneous DBMSs.

The reference architecture diagram for FDBMS


However it is a little bit different for reference architecture for federated MDBS. We still have global
external schema. Which for global users that provide logical data independence.

Global conceptual schema (GCS)

It is a subset of our local conceptual schemas (LCS) consisting of data that each local system
agrees to share.

For example here let's say in the first LCS we have 100 data, 0 local and 70 global and in the second local
conceptual schema LCS we also have 100 data 40 local and 60 global. Only the global data that the
internal system agrees to share will be inside the global cost ratio schema. 70 plus 60 which is we have
130 data that can be used by the global users.
Independent of the reference architecture we can identify a component architecture for a DBMS
consisting of four major components:

Local DBMS LDBMS component

This is to control the local data at each side it has a data base.

Global system catalog

It holds information such as the fragmentation replication allocation schema.

Data communication component

It is a software to enables all sites to communicate with each other.

Distributed DBMS component

You might also like