Distributed Databases

Lecture 3

* Distributed Databases - CSC451 1

Recap
⚫ Distributed Data Processing Vs Distributed Database
⚫ Distributed Databases
⚫ Partitioning
⚫ Replication
⚫ Advantages and Disadvantages of Distributed
Databases

* Distributed Databases - CSC451 2

Outline
⚫ Objectives of a distributed system
⚫ Transparencies in a Distributed DBMS
⚫ Architectural Models for Distributed DBMSs
⚫ Standard ANSI/SPARC Architecture
⚫ Multi-DBMS Architecture
⚫ Distributed DBMS Architecture

* Distributed Databases - CSC451 3

Objectives of a distributed database
⚫ Transparency
⚫ Transparency management of distributed, fragmented
and replicated data.
⚫ simplifies logic of programs
⚫ Data Fragmentation
⚫ achieved if logical object (e.g. file) can be divided into
multiple physical pieces for storage purposes
⚫ Data Replication
⚫ achieved if logical objects can have more than 1 physical
copy

* Distributed Databases - CSC451 4

Objectives of a distributed system
⚫ Local Autonomy
⚫ achieved if systems are distributed consistent with the
logical and physical distribution of the enterprise. It
allows local control over local data, local accountability,
less dependency on remote Data Processing centers
⚫ Incremental Growth Availability and Reliability
⚫ Easier and more economical system expansion

* Distributed Databases - CSC451 5

Transparencies in a Distributed DBMS
⚫ Transparency in a distributed DBMS refers to separation of
the higher-level semantics of a system from lower-level
implementation issues. A transparent system hides the
implementation details from user.

⚫ The advantage of a fully transparent DBMS is the high level

of support that it provides for the development of complex
applications.

* Distributed Databases - CSC451 6

Transparencies in a Distributed DBMS
⚫ Types:
⚫ Data Independence
⚫ Network Transparency
⚫ Replication Transparency
⚫ Fragmentation Transparency
⚫ Language Transparency

* Distributed Databases - CSC451 7

Data Independence
⚫ Immunity of user applications to changes in the
definition and organization of data and vice versa.
⚫ Logical Data Independence
Immunity to changes in logical structures in schema
definition.

⚫ Physical Data Independence

Hides details of the storage structure in Physical data
description.
e.g: The data might be distributed across different storage
hierarchies…There is no difference in the operations carried out
against the data.

* Distributed Databases - CSC451 8

Network (Distribution) transparency
User should be protected from operational details of the network.

⚫ Location Transparency
Commands are independent of both location of the data and the
system on which an operation is carried out.

⚫ Naming Transparency
⚫ Unique name for each object in the database
⚫ Location names are embedded as part of object name

* Distributed Databases - CSC451 9

Replication Transparency
⚫ Various parts of data are replicated (copied) across the network.

⚫ Users should not aware of the existence of copies.(act as a single

copy of the data)

⚫ Data that is commonly accessed by one user can be placed on that

user’s local machine as well as on the machine of another user with
the same access requirements.

Advantages: increases performance, reliability and avalability .

Disadvantages: problems in updating databases.

* Distributed Databases - CSC451 10

 Fragmentation Tranparency
⚫ Data is fragmented into some pieces
and each piece may be located in
different physical locations to
increase performance, availability
and reliability.

⚫ Three types of fragmentation

⚫ Horizontal fragmentation
⚫ Vertical fragmentation
⚫ Hybrid

⚫ Users should not be aware of the

existence of fragments.(act as a single
part)

* Distributed Databases - CSC451 11

Architectural Models for
D-DBMSs
⚫ Architectural models might be determined with possible ways in
which multiple databases may be put together for sharing by
multiple DBMSs.

⚫ Classification might be used that organizes the systems as

characterized with respect to
⚫ the autonomy of local system,
⚫ their distribution,
⚫ their heterogeneity.

* Distributed Databases - CSC451 12

Architectural Models for
D-DBMSs…
⚫ Autonomy refers to distribution of control, not of data.
⚫ Do systems exchange information?
⚫ Independently execute transactions?

⚫ Distribution: components of the systems are located

centrally or distributed over a network

⚫ Heterogeneity
⚫ Various levels (hardware, communications, operating system)

* Distributed Databases - CSC451 13

Architectural Models for D-DBMSs
⚫ Dimensions of autonomy as:

⚫ Design Autonomy: Individual DBMSs are free to use their

data models and transaction management techniques

⚫ Communication Autonomy: Free to decide what type of

information it wants to provide to others

⚫ Execution Autonomy: Free to execute transactions that are

submitted to it, any way that it wants to

* Distributed Databases - CSC451 14

 Some popular autonomus systems

⚫ Tight integration
⚫ Single-image of the entire database is available to any user who wants
to share the information. From the users’ perspective the data is
logically centralized in one database.

⚫ Semiautonomous system(federated)
⚫ Consists of DBMS that can operate independently, but have decided
to participate in a federation to make their local data sharable. Each of
these DBMS determine what parts of their own database are accessible
to users of other DBMSs.

⚫ Total isolation
⚫ Individual systems are stand-alone DBMSs. System does not know
existence of other DBMSs. System does not know how to communicate
with other DBMSs

* Distributed Databases - CSC451 15

Architectural Models for D-DBMSs

* Distributed Databases - CSC451 16

 ANSI/SPARC Architecture
⚫ It is based on data organization.
⚫ Three views
⚫ Internal View
Deals with the physical definition
and organization of the data.
⚫ Conceptual View
Abstract definition of the database.
⚫ External View
Concerned with how users view the
data.
⚫ Transormation between 3 levels is
done by mappings

* Distributed Databases - CSC451 17

 Distributed DBMS Architecture
(From data organizational point of view)

* Distributed Databases - CSC451 18

 Distributed DBMS Architecture
(From data organizational point of view)

⚫ The physical data organization on each machine may be, and probably
different so there needs to be an individual internal schema
definition at each site, which we call the local internal schema(LIS).
⚫ To handle fragmentation and replication, the logical organization of
data each site needs to be described.Local conceptual
schemas(LCS) is needed.
⚫ The global conceptual schema(GCS) describes the logical structure
of data at all the sites. and it is the union of the local conceptual
schemas.
⚫ User and application access to the database is supported by external
schemas(ES)

* Distributed Databases - CSC451 19

Transparency in DDBMS
architecture
⚫ Data independence is supported since the model is an extension
of ANSI/SPARC that provides data independence naturally.

⚫ Location and replication transparencies are supported by

definition of local and global conceptual schemas and mapping
between them.

⚫ Network transparency is supported by the definition of global

conceptual schema.

* Distributed Databases - CSC451 20

 Multi-DBMS Architecture

* Distributed Databases - CSC451 21

 Multi-DBMS Architecture
⚫ Global Conceptual Schema is defined by either
⚫ by integrating local external schemas or
⚫ by integrating parts of the local conceptual
schemas
⚫ Main difference between the GCSs
⚫ integrated DDBMS: mapping from global to
local conceptual schemas
⚫ MDBMS: mapping from local to global
conceptual schemas

* Distributed Databases - CSC451 22

 Multi-DBMS Architecture
⚫ Fundamental difference in architecture: the
global conceptual schema
⚫ in DDBMSs it represents the conceptual view of the
entire database
⚫ in MDBMSs it represents only the collection of
some of the local databases that each local DBMS
wants to share.

* Distributed Databases - CSC451 23

 Distributed
(single db)

Centralized
(single db)

Distributed
* Distributed Databases - CSC451 (multiple db) 24