Database Transaction Processing Systems.pptVIP

ACID Properties of Transactions Chapter 18 Transactions Many enterprises use databases to store information about their state e.g., Balances of all depositors at a bank When an event occurs in the real world that changes the state of the enterprise, a program is executed to change the database state in a corresponding way e.g., Bank balance must be updated when deposit is made Such a program is called a transaction What Does a Transaction Do? Return information from the database RequestBalance transaction: Read customer’s balance in database and output it Update the database to reflect the occurrence of a real world event Deposit transaction: Update customer’s balance in database Cause the occurrence of a real world event Withdraw transaction: Dispense cash (and update customer’s balance in database) Transactions The execution of each transaction must maintain the relationship between the database state and the enterprise state Therefore additional requirements are placed on the execution of transactions beyond those placed on ordinary programs: Atomicity Consistency Isolation Durability Database Consistency Enterprise (Business) Rules limit the occurrence of certain real-world events Student cannot register for a course if the current number of registrants equals the maximum allowed Correspondingly, allowable database states are restricted cur_reg = max_reg These limitations are called (static) integrity constraints: assertions that must be satisfied by all database states (state invariants). Database Consistency(state invariants) Other static consistency requirements are related to the fact that the database might store the same information in different ways cur_reg = |list_of_registered_students| Such limitations are also expressed as integrity constraints Database is consistent if all static integrity constraints are satisfied Transaction Consistency A consistent database state does not necessarily model the actual state of the enterprise A deposit tra