1 Chapter 22 Distributed DBMS Concepts and Design CS 157B Edward Chen.

Slides:



Advertisements
Similar presentations
Database Systems: Design, Implementation, and Management
Advertisements

Database Architectures and the Web
Enterprise Systems Distributed databases and systems - DT
Distributed databases
Transaction.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Chapter 13 (Web): Distributed Databases
Manajemen Basis Data Pertemuan 9 Matakuliah: M0264/Manajemen Basis Data Tahun: 2008.
1 Minggu 12, Pertemuan 23 Introduction to Distributed DBMS (Chapter , 22.6, 3rd ed.) Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
ABCSG - Distributed Database 1 Data Management Distributed Database Data Replication.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide
Distributed Database Management Systems
Chapter 9 : Distributed Database.
Overview Distributed vs. decentralized Why distributed databases
1 9 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 9 Database Management Approaches.
©Silberschatz, Korth and Sudarshan19.1Database System Concepts Lecture-10 Distributed Database System A distributed database system consists of loosely.
Chapter 12 Distributed Database Management Systems
Chapter 3 : Distributed Data Processing
Definition of terms Definition of terms Explain business conditions driving distributed databases Explain business conditions driving distributed databases.
DISTRIBUTED DATABASE MANAGEMENT SYSTEM CHAPTER 07.
Distributed databases
DATABASE MANAGEMENT SYSTEMS 2 ANGELITO I. CUNANAN JR.
Distributed Database and Replication. Distributed Database A logically interrelated collection of shared data and a description of this data physically.
Distributed Databases and DBMSs: Concepts and Design
Distributed Database The University of California Berkeley Extension Copyright © 2011 Patrick McDermott.
Database Architectures and the Web
1 Distributed and Parallel Databases. 2 Distributed Databases Distributed Systems goal: –to offer local DB autonomy at geographically distributed locations.
12 1 Chapter 12 Distributed Database Management Systems Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database Architectures and the Web Session 5
Distributed DBMSs - Concepts and Design Transparencies
Database Design – Lecture 16
III. Current Trends: 1 - Distributed DBMSsSlide 1/32 III. Current Trends Part 1: Distributed DBMSs: Concepts and Design Lecture 12 (2 hours) Lecturer:
ENTERPRISE PROGRAMMING
DISTRIBUTED DATABASES IN ADBMS Shilpa Seth
Session-9 Data Management for Decision Support
Distributed and mobile DBMSs Transparencies. ©Pearson Education 2009 Chapter 16 - Objectives Main concepts of distributed DBMSs (DDBMSs) Differences between.
Massively Distributed Database Systems - Distributed DBS Spring 2014 Ki-Joune Li Pusan National University.
Lecture 5: Sun: 1/5/ Distributed Algorithms - Distributed Databases Lecturer/ Kawther Abas CS- 492 : Distributed system &
Session-8 Data Management for Decision Support
10 1 Chapter 10 Distributed Database Management Systems Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 12 Distributed Database Management Systems.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 12 Distributed Database Management Systems.
Distributed Database Systems Overview
10 1 Chapter 10 Distributed Database Management Systems Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Multiprossesors Systems.. What are Distributed Databases ? “ A Logically interrelated collection of shared data ( and a description of this data) physically.
The Evolution of Distributed DBMS 4Social and Technical Changes in the 1980’s u Business operations became more decentralized geographically. u Competition.
DDBMS Distributed Database Management Systems Fragmentation
Distributed DBMSs- Concept and Design Jing Luo CS 157B Dr. Lee Fall, 2003.
Kjell Orsborn UU - DIS - UDBL DATABASE SYSTEMS - 10p Course No. 2AD235 Spring 2002 A second course on development of database systems Kjell.
Distributed Databases
ASMA AHMAD 28 TH APRIL, 2011 Database Systems Distributed Databases I.
1 Distributed Databases BUAD/American University Distributed Databases.
Distributed Database. Introduction A major motivation behind the development of database systems is the desire to integrate the operational data of an.
Distributed database system
Topic Distributed DBMS Database Management Systems Fall 2012 Presented by: Osama Ben Omran.
Chapter 12 Distributed Data Bases. Learning Objectives What a distributed database management system (DDBMS) is and what its components are How database.
Distributed Database Management Systems. Reading Textbook: Ch. 1, Ch. 3 Textbook: Ch. 1, Ch. 3 For next class: Ch. 4 For next class: Ch. 4 FarkasCSCE.
 Distributed Database Concepts  Parallel Vs Distributed Technology  Advantages  Additional Functions  Distribution Database Design  Data Fragmentation.
Chapter 24 Distributed DBMSs – Concepts and Design Pearson Education © 2014.
Distributed Database Design Bayu Adhi Tama, MTI Fasilkom-Unsri Adapted from Connolly, et al., Database Systems 4 th Edition, Pearson Education Limited,
1 Information Retrieval and Use De-normalisation and Distributed database systems Geoff Leese September 2008, revised October 2009.
Distributed DBMSs – Concepts and Design Chapter 24 in Textbook.
CMS Advanced Database and Client-Server Applications Distributed Databases slides by Martin Beer and Paul Crowther Connolly and Begg Chapter 22.
DISTRIBUTED DATABASES AND DDBMS. Learning Objectives  Describe various DDBMS implementations  Explain how database design affects the DDBMS environment.
1 Chapter 22 Distributed DBMSs - Concepts and Design Simplified Transparencies © Pearson Education Limited 1995, 2005.
Distributed Database Concepts
Distributed Database Management Systems
Distributed DBMS Concepts of Distributed DBMS
Distributed Databases and DBMSs: Concepts and Design
Presentation transcript:

1 Chapter 22 Distributed DBMS Concepts and Design CS 157B Edward Chen

2 Introduction Distributed Database changes the way of data sharing, conceptually from centralization into decentralization. Distributed Database changes the way of data sharing, conceptually from centralization into decentralization. Development of computer networks promotes a decentralized mode of work. Development of computer networks promotes a decentralized mode of work. Development of distributed systems should improve the sharing ability of the data and the efficiency of data access Development of distributed systems should improve the sharing ability of the data and the efficiency of data access Distributed systems should help resolve the "islands of information" problem Distributed systems should help resolve the "islands of information" problem

3 Concepts Distributed database A logically interrelated collection of shared data and description of this data, physically distribute over a computer network. Distributed DBMS The software system that permits the management of the distributed databases and makes the distribution transparent to users.

4 Concepts (cont’d)  In a distributed DBMS, single logical database is split into a number of fragments.  Each fragment is stored on one or more computers under the control of a separate DBMS  with the computer connected to a network. Each site is capable of independently processing user requests that require access to local data and is also capable of processing data stored on other computers in the network.

5 Concepts (cont’d) There are two applications There are two applications 1) local application: do not require data from other sites 2) global application: do require data from other sites Distributed DBMS need to have at least one global application. Distributed DBMS need to have at least one global application.

6 Concepts (cont’d) DBMS have following characteristics: A collection of logically related shared data A collection of logically related shared data The data is split into number of fragments The data is split into number of fragments Fragments may be replicated Fragments may be replicated Fragments/replicas are allocated to sites. Fragments/replicas are allocated to sites. The sites are linked with computer network. The sites are linked with computer network. The data at each site is under the control of a DBMS The data at each site is under the control of a DBMS The DBMS at each site can handle local applications autonomously. The DBMS at each site can handle local applications autonomously. Each DBMS participates in at least one global application. Each DBMS participates in at least one global application.

7 Distributed Database Management System It is not necessary for every site in the system to have its own local database as shown It is not necessary for every site in the system to have its own local database as shown The system is expected to make the distribution transparent to the user The system is expected to make the distribution transparent to the user Distributed database is split into fragments that can be stored on different computers and perhaps replicated Distributed database is split into fragments that can be stored on different computers and perhaps replicated The objective of the transparency is to make the distributed system to appear like a centralized system The objective of the transparency is to make the distributed system to appear like a centralized system

8 Distributed Processing The system consists of data that is physically distributed across the network. If the data is centralized, even though the users may be accessing the data over the network, it is not considered as distributed DBMS, simply distributed processing

9 Advantages Reflects organizational structure Reflects organizational structure Improved shareablility and local autonomy Improved shareablility and local autonomy Improved availability Improved availability Improved reliability Improved reliability Improved performance Improved performance Modular growth Modular growth Less danger on single-point failure Less danger on single-point failure

10 Disadvantages Complexity Complexity Cost Cost Security Security Integrity control more difficult Integrity control more difficult Lack of standards Lack of standards Lack of experience Lack of experience Database design more complex Database design more complex Possible slow response Possible slow response

11 Homogeneous and Heterogeneous DDBMSs Homogeneous DDBMS  In homogeneous DDBMS, all sites use the same DBMS product.  Much easier to design and manage.  This design provides incremental growth by making additional new sites to DDBMS easy  Allows increased performance by exploiting the parallel processing capability of multiple sites.

12 Homogeneous and Heterogeneous DDBMSs (cont’d) Heterogeneous DDBMSs In heterogeneous DDBMS, all sites may run different DBMS products, which need not to be based on the same underlying data model and so the system may be composed of RDBMS, ORDBMS and OODBMS products. In heterogeneous system, communication between different DBMS are required for translations. In order to provide DBMS transparency, users must be able to make requests in the language of the DBMS at their local site. Data from the other sites may have different hardware, different DBMS products and combination of different hardware and DBMS products. The task for locating those data and performing any necessary translation are the abilities of heterogeneous DDBMS.

13 Components Architecture of DDBMS Component Architecture for a DDBMS Local DBMS (LDBMS) component - It has its own local system catalog that stores information about the data held at that site. Data communications (DC) component – is the software that enables all sites to communicate with each other. Global System Catalog (GSC) - The GSC holds information specific to the distributed nature of the system, such as the fragmentation and allocation schemas. Distributed DBMS component - is the controlling unit of the entire system.

14 Components Architecture of DBMS (cont’d) Fig. components of DDBMS

15 FRAGMENTATION FRAGMENTATION Why fragmentation? · Usage: Applications work with views rather than entire relations · Efficiency: Data is stored close to where it is mostly frequently used · Parallelism: With fragments are the unit of distribution, a transaction can be divided into several subqueries that operate on fragments. · Security : Data not required by local applications is not restored, and consequently not available to unauthorized users..Performance: The performance of global applications that require data from several fragments located at different sites may be slower.

16 FRAGMENTATION (cont’d) Types of fragmentation · Horizontal fragmentation : a subset of the tuples of a relation, defined as sp(R), where p is a predicate based on one or more attributes of there relation. · Vertical fragmentation : a subset of the attributes of a relation, denoted as Pa1, a2,.., an (R), where a1, a2,.., an are attributes of the relation R. · Mixed fragmentation : A horizontal fragment that is subsequently vertically fragmented, or a vertical fragment that is then horizontally fragmented.

17 FRAGMENTATION (cont’d)  Selection S p(R) - defines a relation that contains only those tuples of R that satisfy the specified condition (predicate p). The same as horizontal fragmentation.  Projection P a1, a2,.., an (R) - defines a relation that contains a vertical subset of R, extracting the values of specified attributes and eliminating duplicates. The same as vertical fragmentation.

18 Summary A distributed database is a collection of multiple, logically interrelated collection of shared data which is physically distributed over a computer network. Basically, a DDBMS is different from a client-server system, even though the client-server architecture can be used to provide distributed DBMSs. Both Top-down and Bottom-up design approaches can be used to design DDBMS.

19 Summary (cont’d) A relation may be divided into a number of sub relations called fragments, which may be horizontal, vertical, mixed. The three correctness rules of fragmentation are: completeness, reconstruction, and disjoitness. There are four allocation strategies regarding the placement of data: centralized, partitioned, complete replication and selected replication.

20 The End