Question 8. What is Distributed Database Management System?

Discuss some problems to which subjects to

DDBMS.

Answer. A distributed database is a collection of multiple interconnected databases, which are spread
physically across various locations that communicate via a computer network.

1Features:
·Databases in the collection are logically interrelated with each other. Often they represent a single
logical database.
·Data is physically stored across multiple sites. Data in each site can be managed by a DBMS
independent of the other sites.
·The processors in the sites are connected via a network. They do not have any multiprocessor
configuration.
·A distributed database is not a loosely connected file system.
·A distributed database incorporates transaction processing, but it is not synonymous with a
transaction processing system.

2Distributed Database Management System

A distributed database management system (DDBMS) is a centralized software system that manages a
distributed database in a manner as if it were all stored in a single location.

2.1Features
·It is used to create, retrieve, update and delete distributed databases.
·It synchronizes the database periodically and provides access mechanisms by the virtue of which the
distribution becomes transparent to the users.
·It ensures that the data modified at any site is universally updated.
·It is used in application areas where large volumes of data are processed and accessed by numerous
users simultaneously.
·It is designed for heterogeneous database platforms.
·It maintains confidentiality and data integrity of the databases.

3Factors Encouraging DDBMS:

The following factors encourage moving over to DDBMS ?
·Distributed Nature of Organizational Units ? Most organizations in the current times are
subdivided into multiple units that are physically distributed over the globe. Each unit requires its own
set of local data. Thus, the overall database of the organization becomes distributed.
·Need for Sharing of Data ? The multiple organizational units often need to communicate with each
other and share their data and resources. This demands common databases or replicated databases that
should be used in a synchronized manner.
·Support for Both OLTP and OLAP ? Online Transaction Processing (OLTP) and Online Analytical
Processing (OLAP) work upon diversified systems which may have common data. Distributed
database systems aid both these processing by providing synchronized data.
·Database Recovery ? One of the common techniques used in DDBMS is replication of data across
different sites. Replication of data automatically helps in data recovery if database in any site is
damaged. Users can access data from other sites while the damaged site is being reconstructed. Thus,
database failure may become almost inconspicuous to users.
·Support for Multiple Application Software ? Most organizations use a variety of application
software each with its specific database support. DDBMS provides a uniform functionality for using
the same data among different platforms.
4Advantages of Distributed Databases:
Following are the advantages of distributed databases over centralized databases.
Modular Development ? If the system needs to be expanded to new locations or new units, in centralized
database systems, the action requires substantial efforts and disruption in the existing functioning. However, in
distributed databases, the work simply requires adding new computers and local data to the new site and
finally connecting them to the distributed system, with no interruption in current functions.
More Reliable ? In case of database failures, the total system of centralized databases comes to a halt.
However, in distributed systems, when a component fails, the functioning of the system continues may be at a
reduced performance. Hence DDBMS is more reliable.
Better Response ? If data is distributed in an efficient manner, then user requests can be met from local data
itself, thus providing faster response. On the other hand, in centralized systems, all queries have to pass
through the central computer for processing, which increases the response time.
Lower Communication Cost ? In distributed database systems, if data is located locally where it is mostly
used, then the communication costs for data manipulation can be minimized. This is not feasible in centralized
systems.

5Adversities of Distributed Databases

Following are some of the adversities associated with distributed databases.
·Need for complex and expensive software ? DDBMS demands complex and often expensive
software to provide data transparency and co-ordination across the several sites.
·Processing overhead ? Even simple operations may require a large number of communications and
additional calculations to provide uniformity in data across the sites.
·Data integrity ? The need for updating data in multiple sites pose problems of data integrity.
·Overheads for improper data distribution ? Responsiveness of queries is largely dependent upon
proper data distribution. Improper data distribution often leads to very slow response to user requests.

The distribution of data and applications has potential advantages over traditional centralized database
systems. Unfortunately, there are also disadvantages; in this section we review the advantages and
disadvantages of DDBMS.
Advantages
There are following advantages of DDBMs:

5.1Reflects organizational structure

Many organizations are naturally distributed over several locations. For example, a bank has many offices in
different cities. It is natural for databases used in such an application to be distributed over these locations. A
bank may keep a database at each branch office containing details such things as the staff that work at that
location, the account information of customers etc.
The staff at a branch office will make local inquiries of the database. The company headquarters may wish to
make global inquiries involving the access of data at all or a number of branches.

5.2Improved share ability and local autonomy

The geographical distribution of an organization can be reflected in the distribution of the data; users at one
site can access data stored at other sites. Data can be placed at the site close to the users who normally use
that data. In this way, users have local control of the data, and they can consequently establish and enforce
local policies regarding the use of this data. A global database administrator (DBA) is responsible for the
entire system. Generally, part of this responsibility is assigned the local level, so that the local DBA can
manage the local DBMS.
5.3Improved availability
In a centralized DBMS, a computer failure terminates the applications of the DBMS. However, a failure at
one site of a DDBMS, or a failure of a communication link making\ some sites inaccessible, does not make the
entire system in opera bite. Distributed DBMSs are designed to continue to function despite such failures. If a
single node fails, the system may be able to reroute the failed node's requests to another site.

5.4Improved reliability
As data may be replicated so that it exists at more than one site, the failure of a node or a communication link
does not necessarily make the data inaccessible.

5.5Improved Performance
As the data is located near the site of 'greatest demand', and given the inherent parallelism of distributed
DBMSs, speed of database access may be better than that achievable from a remote centralized database.
Furthermore, since each site handles only a part of the entire database, there may not be the same contention
for CPU and I/O services as characterized by a centralized DBMS.

5.6Economics
It is now generally accepted that it costs much less to create a system of smaller computers with the equivalent
power of a single large computer. This makes it more cost effective for corporate divisions and departments to
obtain separate computers. It is also much more cost-effective to add workstations· to a network than to
update a mainframe system.
The second potential cost saving occurs where database are geographically remote and the applications require
access to distributed data. In such cases, owing to the relative expense of data being transmitted across the
network as opposed to the cost of local access, it may be much more economical to partition the application
and perform the processing locally at each site.

5.7Modular growth
In a distributed environment, it is much easier to handle expansion. New sites can be added to the network
without affecting the operations of other sites. This flexibility allows an organization to expand relatively
easily. Adding processing and storage power to the network can usually handle the increase in database size. In
a centralized DBMS, growth may entail changes to both hardware (the procurement of a more powerful
system) and software (the procurement of a more powerful or more configurable DBMS).

6Disadvantages of DDBMS
There are following disadvantages of DDBMSs:

6.1Complexity
A distributed DBMS that hides the distributed nature from the user and provides an acceptable level of
performance, reliability, availability is inherently more complex then a centralized DBMS. The fact that data
can be replicated also adds an extra level of complexity to the distributed DBMS. If the software does not
handle data replication adequately, there wi1l be degradation in availability, reliability and performance
compared with the centralized system, and the advantages we cites above will become disadvantages.

6.2Cost
Increased complexity means that we can expect the procurement and maintenance costs for a DDBMS to be
higher than those for a centralized DBMS. Furthermore, a distributed
DBMS requires additional hardware to establish a network between sites. There are ongoing communication
costs incurred with the use of this network. There are also additional labor costs to manage and maintain the
local DBMSs and the underlying network.
6.3Security
In a centralized system, access to the data can be easily controlled. However, in a distributed DBMS not only
does access to replicated data have to be controlled in multiple locations but also the network itself has to be
made secure. In the past, networks were regarded as an insecure communication medium. Although this is still
partially true, significant developments have been made to make networks more secure.

6.4Integrity control more difficult

Database integrity refers to the validity and consistency of stored data. Integrity is usually expressed in terms
of constraints, which are consistency rules that the database is not permitted to violate. Enforcing integrity
constraints generally requires access to a large amount of data that defines the constraints. In a distributed
DBMS, the communication and processing costs that are required to enforce integrity constraints are high as
compared to centralized system.

6.5Lack of Standards
Although distributed DBMSs depend on effective communication, we are only now starting to see the
appearance of standard communication and data access protocols. This lack of standards has significantly
limited the potential of distributed DBMSs. There are also no tools or methodologies to help users convert a
centralized DBMS into a distributed DBMS

6.6Lack of experience
General-purpose distributed DBMSs have not been widely accepted, although many of the protocols and
problems are well understood. Consequently, we do not yet have the same level of experience in industry as we
have with centralized DBMSs. For a prospective adopter of this technology, this may be a significant
deterrent.

6.7Database design more complex

Besides the normal difficulties of designing a centralized database, the design of a distributed database has to
take account of fragmentation of data, allocation of fragmentation to specific sites, and data replication.

A distributed database is a collection of multiple interconnected databases, which are spread physically
across various locations that communicate via a computer network.

7Features
·Databases in the collection are logically interrelated with each other. Often they represent a single
logical database.
·Data is physically stored across multiple sites. Data in each site can be managed by a DBMS
independent of the other sites.
·The processors in the sites are connected via a network. They do not have any multiprocessor
configuration.
·A distributed database is not a loosely connected file system.
·A distributed database incorporates transaction processing, but it is not synonymous with a
transaction processing system.

8Distributed Database Management System

A distributed database management system (DDBMS) is a centralized software system that manages a
distributed database in a manner as if it were all stored in a single location.
8.1Features
·It is used to create, retrieve, update and delete distributed databases.
·It synchronizes the database periodically and provides access mechanisms by the virtue of which the
distribution becomes transparent to the users.
·It ensures that the data modified at any site is universally updated.
·It is used in application areas where large volumes of data are processed and accessed by numerous
users simultaneously.
·It is designed for heterogeneous database platforms.
·It maintains confidentiality and data integrity of the databases.

9Factors Encouraging DDBMS

The following factors encourage moving over to DDBMS ?
·Distributed Nature of Organizational Units ? Most organizations in the current times are
subdivided into multiple units that are physically distributed over the globe. Each unit requires its own
set of local data. Thus, the overall database of the organization becomes distributed.
·Need for Sharing of Data ? The multiple organizational units often need to communicate with each
other and share their data and resources. This demands common databases or replicated databases that
should be used in a synchronized manner.
·Support for Both OLTP and OLAP ? Online Transaction Processing (OLTP) and Online Analytical
Processing (OLAP) work upon diversified systems which may have common data. Distributed
database systems aid both these processing by providing synchronized data.
·Database Recovery ? One of the common techniques used in DDBMS is replication of data across
different sites. Replication of data automatically helps in data recovery if database in any site is
damaged. Users can access data from other sites while the damaged site is being reconstructed. Thus,
database failure may become almost inconspicuous to users.
·Support for Multiple Application Software ? Most organizations use a variety of application
software each with its specific database support. DDBMS provides a uniform functionality for using
the same data among different platforms.

10Advantages of Distributed Databases

Following are the advantages of distributed databases over centralized databases.
Modular Development ? If the system needs to be expanded to new locations or new units, in centralized
database systems, the action requires substantial efforts and disruption in the existing functioning. However, in
distributed databases, the work simply requires adding new computers and local data to the new site and
finally connecting them to the distributed system, with no interruption in current functions.
More Reliable ? In case of database failures, the total system of centralized databases comes to a halt.
However, in distributed systems, when a component fails, the functioning of the system continues may be at a
reduced performance. Hence DDBMS is more reliable.
Better Response ? If data is distributed in an efficient manner, then user requests can be met from local data
itself, thus providing faster response. On the other hand, in centralized systems, all queries have to pass
through the central computer for processing, which increases the response time.
Lower Communication Cost ? In distributed database systems, if data is located locally where it is mostly
used, then the communication costs for data manipulation can be minimized. This is not feasible in centralized
systems.

11Adversities of Distributed Databases

Following are some of the adversities associated with distributed databases.
 ·Need for complex and expensive software ? DDBMS demands complex and often expensive
software to provide data transparency and co-ordination across the several sites.
·Processing overhead ? Even simple operations may require a large number of communications and
additional calculations to provide uniformity in data across the sites.
·Data integrity ? The need for updating data in multiple sites pose problems of data integrity.
·Overheads for improper data distribution ? Responsiveness of queries is largely dependent upon
proper data distribution. Improper data distribution often leads to very slow response to user requests.
Two processes ensure that the distributed databases remain up-to-date and current: replication and duplication.
1Replication involves using specialized software that looks for changes in the distributive database. Once the
changes have been identified, the replication process makes all the databases look the same. The replication
process can be complex and time-consuming depending on the size and number of the distributed databases.
This process can also require a lot of time and computer resources.
2Duplication, on the other hand, has less complexity. It basically identifies one database as a master and then
duplicates that database. The duplication process is normally done at a set time after hours. This is to ensure
that each distributed location has the same data. In the duplication process, users may change only the master
database. This ensures that local data will not be overwritten.
Both replication and duplication can keep the data current in all distributive locations.
Besides distributed database replication and fragmentation, there are many other distributed database design
technologies. For example, local autonomy, synchronous and asynchronous distributed database technologies.
These technologies' implementations can and do depend on the needs of the business and the
sensitivity/confidentiality of the data stored in the database, and the price the business is willing to spend on
ensuring data security, consistency and integrity.