UNIFOR University of Fortaleza Brazil University of Kaiserslautern Germany  Angelo Brayner CoopIS - Trento, September 20011 Global Semantic Serializability:

Slides:



Advertisements
Similar presentations
Universität Karlsruhe (TH) TAV 10© 2007 Univ,Karlsruhe, IPD, Prof. Lockemann/Prof. Böhm Chapter 10 Distributed Transactions: Synchronization.
Advertisements

Serializability in Multidatabases Ramon Lawrence Dept. of Computer Science
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Chapter 16.
TRANSACTION PROCESSING SYSTEM ROHIT KHOKHER. TRANSACTION RECOVERY TRANSACTION RECOVERY TRANSACTION STATES SERIALIZABILITY CONFLICT SERIALIZABILITY VIEW.
Chapter 15: Transactions Transaction Concept Transaction Concept Concurrent Executions Concurrent Executions Serializability Serializability Testing for.
COMP 655: Distributed/Operating Systems Summer 2011 Dr. Chunbo Chu Week 7: Consistency 4/13/20151Distributed Systems - COMP 655.
Principles of Transaction Management. Outline Transaction concepts & protocols Performance impact of concurrency control Performance tuning.
Cs4432concurrency control1 CS4432: Database Systems II Lecture #22 Concurrency Control Professor Elke A. Rundensteiner.
Transactions (Chapter ). What is it? Transaction - a logical unit of database processing Motivation - want consistent change of state in data Transactions.
Fakultas Ilmu Komputer UI 1 Exercise A series of actions to be taken on the database such that either all actions are completed successfully, or none of.
Transaction Management Overview. Transactions Concurrent execution of user programs is essential for good DBMS performance. –Because disk accesses are.
Page 1 Integrating Multiple Data Sources using a Standardized XML Dictionary Ramon Lawrence Integrating Multiple Data Sources using a Standardized XML.
ICOM 6005 – Database Management Systems Design Dr. Manuel Rodríguez-Martínez Electrical and Computer Engineering Department Lecture 16 – Intro. to Transactions.
Simulating MDBS Transaction Management Protocols TRLabs - Winnipeg Researchers: Ramon Lawrence, Aruna Adil, Ken Barker University of Manitoba Researchers:
Distributed DBMSPage © 1998 M. Tamer Özsu & Patrick Valduriez Outline Introduction Background Distributed DBMS Architecture Distributed Database.
Transaction Management and Concurrency Control
Distributed DBMSPage © 1998 M. Tamer Özsu & Patrick Valduriez Outline Introduction Background Distributed DBMS Architecture Distributed Database.
Chapter 11 Grid Concurrency Control 11.1 A Grid Database Environment 11.2 An Example 11.3 Grid Concurrency Control (GCC) 11.4 Correctness of GCC 11.5 Features.
Overview Distributed vs. decentralized Why distributed databases
Page 1 Simulating MDBS Transaction Management Protocols Ramon Lawrence, Ken Barker, Aruna Adil Simulating MDBS Transaction Management Protocols Ramon Lawrence,
All of ERD (Ch 3) plus: – Class/subclass relationships – Inheritance – Specialization – Generalization – Category.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 10 Transaction Management and Concurrency Control.
ICS (062)CC in Adv. DB Applications1 Concurrency Control in Advanced Database Applications Dr. Muhammad Shafique 31 March 2007.
System Catalogue v Stores data that describes each database v meta-data: – conceptual, logical, physical schema – mapping between schemata – info for query.
© 1998 Singh & Huhns1 Database Integration. © 1998 Singh & Huhns2 Dimensions of Integration Existence of global schema Location transparency: same view.
BACS 485—Database Management Concurrency Control Overview of Database Concurrency Control.
Transaction Management and Concurrency Control
Outline Introduction Background Distributed Database Design
Distributed databases
CS4432: Database Systems II Transaction Management Motivation 1.
Copyright © 2004 Pearson Education, Inc.. Chapter 17 Introduction to Transaction Processing Concepts and Theory.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Chapter 16.
1 Transaction Management Overview Chapter Transactions  Concurrent execution of user programs is essential for good DBMS performance.  Because.
Database Management Systems, 2 nd Edition. R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Chapter 18.
CST203-2 Database Management Systems Lecture 2. One Tier Architecture Eg: In this scenario, a workgroup database is stored in a shared location on a single.
Presented by Dr. Greg Speegle April 12,  Two-phase commit slow relative to local transaction processing  CAP Theorem  Option 1: Reduce availability.
Session-9 Data Management for Decision Support
BIS Database Systems School of Management, Business Information Systems, Assumption University A.Thanop Somprasong Chapter # 10 Transaction Management.
Database Management Systems, 2 nd Edition. R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Lecture 21 Ramakrishnan - Chapter 18.
CS 162 Discussion Section Week 9 11/11 – 11/15. Today’s Section ●Project discussion (5 min) ●Quiz (10 min) ●Lecture Review (20 min) ●Worksheet and Discussion.
Distributed Database Systems Overview
Database Systems/COMP4910/Spring05/Melikyan1 Transaction Management Overview Unit 2 Chapter 16.
1 Transaction Management Overview Chapter Transactions  Concurrent execution of user programs is essential for good DBMS performance.  Because.
Module Coordinator Tan Szu Tak School of Information and Communication Technology, Politeknik Brunei Semester
1 Concurrency Control II: Locking and Isolation Levels.
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.
1 By Paul Murray Claire McQuade Kashif Rafiq David Miller.
Transaction Management Overview. Transactions Concurrent execution of user programs is essential for good DBMS performance. – Because disk accesses are.
1 CSE 480: Database Systems Lecture 24: Concurrency Control.
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.
Concurrency (cont.) Schedule. In multiprogramming environment, Several transaction run concurrently Database consistency can be destroy Schedules to ensure.
1 Advanced Database Concepts Transaction Management and Concurrency Control.
1 Lecture 4: Transaction Serialization and Concurrency Control Advanced Databases CG096 Nick Rossiter [Emma-Jane Phillips-Tait]
Transaction Management and Recovery, 2 nd Edition. R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Chapter 18.
Multidatabase Transaction Management COP5711. Multidatabase Transaction Management Outline Review - Transaction Processing Multidatabase Transaction Management.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 10 Transaction Management and Concurrency Control.
10 Transaction Management and Concurrency Control MIS 304 Winter 2005.
1 Controlled concurrency Now we start looking at what kind of concurrency we should allow We first look at uncontrolled concurrency and see what happens.
ICOM 6005 – Database Management Systems Design Dr. Manuel Rodríguez-Martínez Electrical and Computer Engineering Department Lecture 16 – Intro. to Transactions.
Chapter 8: Concurrency Control on Relational Databases
Transaction Properties
Distributed Transactions
Chapter 10 Transaction Management and Concurrency Control
Outline Introduction Background Distributed DBMS Architecture
Database Security Transactions
Introduction of Week 13 Return assignment 11-1 and 3-1-5
Outline Introduction Background Distributed DBMS Architecture
Presentation transcript:

UNIFOR University of Fortaleza Brazil University of Kaiserslautern Germany  Angelo Brayner CoopIS - Trento, September Global Semantic Serializability: An Approach to Increase Concurrency in Multidatabase Systems Angelo Brayner Theo Härder

UNIFOR  Angelo BraynerCoopIS - Trento, September Contents Motivation Multidatabase System Model Global Semantic Serializability Concurrency Control Protocols Conclusions

UNIFOR  Angelo BraynerCoopIS - Trento, September Motivation (1) Integration of heterogeneous databases is a strategic requirement Integration of heterogeneous databases in a enterprise Integration of heterogeneous web databases  Web as a large collection of distributed autonomous and heterogeneous databases Integration of ubiquitous databases  mobile heterogeneous databases providing data everywhere

UNIFOR  Angelo BraynerCoopIS - Trento, September Motivation (2) Multidatabase technology Efficient solution for integrating a collection of autonomous and heterogeneous databases  Local databases Created independently without considering the possibility of being integrated in the future Operate autonomously Local autonomy is a key feature  Multidatabase Collection of local databases

UNIFOR  Angelo BraynerCoopIS - Trento, September Motivation (3) Multidatabase System (MDBS) Software component to manage a multidatabase Provides DBMS functionalities Multidatabase environment Global transactions  Submitted to the MDBS Access and update local database objects Local transactions  Submitted to local database systems

UNIFOR  Angelo BraynerCoopIS - Trento, September Motivation (4) Classical transaction-processing Model "Syntactic" serializability  Serialization order of all active transactions must be known For identifying correct execution of concurrent transactions Efficient criterion for synchronizing operations of short transactions

UNIFOR  Angelo BraynerCoopIS - Trento, September Motivation (5) Concurrency control problem in MDBSs Global transactions  Involve operations on multiple local databases Long-living transactions MDBS does not have any information about the execution (serialization) order of local transactions Classical transaction model is inefficient for solving the CC problem in MDBSs

UNIFOR  Angelo BraynerCoopIS - Trento, September Multidatabase System Model (1) LDBS n Local Transactions SUB jn SUB in Global Recovery Manager Global Log Global Transaction Manager MDBS GjGj GiGi Global Transactions Global Scheduler Interface Server 1 Log Interface Server n DB DBMS Local Transactions SUB i1 SUB j1 LDBS 1 DB DBMS

UNIFOR  Angelo BraynerCoopIS - Trento, September Multidatabase System Model (2) MDBS 1. A set LD ={LDBS 1, LDBS 2, …, LDBS n } of local database systems 2. A set L ={L 1, L 2, …, L n }  Each L K represents a set of local transactions executed at LDBS K 3. A set G ={G 1, G 2, …, G n } of global transactions

UNIFOR  Angelo BraynerCoopIS - Trento, September Multidatabase System Model (3) Local Schedule S K Models the execution of interleaved operations belonging to local and global transactions  Executed at LDBS K Global Schedule S G Models the execution of all local schedules

UNIFOR  Angelo BraynerCoopIS - Trento, September GS -Serializability Model (1) Assumptions An MDBS integrates a collection of pre- existing local databases (LDBs) A collection of disjoint sets of objects  Each set represents a single local database  Semantic Unit An update operation executed by a global transaction G on an object of a particular semantic unit does not depend on values of objects belonging to other semantic units previously read by G An update operation executed by a global transaction G on an object of a particular semantic unit does not depend on values of objects belonging to other semantic units previously read by G

UNIFOR  Angelo BraynerCoopIS - Trento, September GS -Serializability Model (2) Module-structured Transaction Operations are grouped into subsequences  Modules  Encompasses operations on objects of only one semantic unit Example  DB={A, B, C, D, E, F, G} A, B, C  SU LDBS1 ={A, B, C} D, E, F, G  SU LDBS2 ={D, E, F, G} 4 T 1 = r 1 (G) w 1 (E) w 1 (C) r 1 (B) 8 T 2 = r 2 (G) w 2 (C) w 2 (E) r 1 (B) Module

UNIFOR  Angelo BraynerCoopIS - Trento, September GS -Serializability Model (3) GS -Serial Global Schedule Local schedules are conflict serializable and Serial execution of modules belonging to global transactions Example CBAB G 1 =r 1 (G)w 1 (E)w 1 (C)r 1 (B); G 2 =r 2 (A)w 2 (B)w 2 (D)r 2 (E) ABCB S C = r 2 (A)w 2 (B)r 1 (G)w 1 (E)w 2 (D)r 2 (E)w 1 (C)r 1 (B)  S C is GS -Serial ì S C is not conflict serializable

UNIFOR  Angelo BraynerCoopIS - Trento, September GS -Serializability Model (4) GS -Serial Schedules preserve multidatabase consistency Correctness criterion for MDBSs GS -Serializable Schedule S Local schedules are conflict serializable and The execution order of global transactions in S is conflict equivalent to the execution of a GS -Serial schedule over the same set of transactions

UNIFOR  Angelo BraynerCoopIS - Trento, September GS -Serializability Model (5) Identifying GS -Serializable Schedule Since existing DBMSs yield conflict serializable schedules + The GTM has solely to verify the execution order of global transactions  A graph-based method The Semantic Serialization Graph (SSG)

UNIFOR  Angelo BraynerCoopIS - Trento, September Concurrency Control in MDBSs Concurrency Control Protocols Conservative  Based on a locking mechanism Aggressive  Management of an always acyclic graph Based on the SSG

UNIFOR  Angelo BraynerCoopIS - Trento, September Conclusions GS -Serializability Model Increases concurrency in MDBSs  More permissive than syntactic serializability Increases concurrency in mediator-based systems  Each web database can be seen as a semantic unit Can be applied to control concurrency in ubiquitous database  Mobile database can be defined as a semantic unit