数据库系统概念PPT十五,对应原版教材五版.ppt

Chapter 15: Transactions Transaction Concept Concurrent Executions Serializability Testing for Serializability Recoverability Transaction Definition in SQL Transaction Concept E.g. Transaction to transfer $50 from account A to account B: 1. read(A) 4. read(B) 2. A := A – 50 5. B := B + 50 3. write(A) 6. write(B A transaction is a unit of program execution that accesses and possibly updates various data items. A transaction must see a consistent database. During transaction execution the database may be inconsistent. When the transaction is committed, the database must be consistent. Two main issues to deal with: Failures of various kinds, such as hardware failures and system crashes Concurrent execution of multiple transactions ACID Properties Atomicity. Either all operations of the transaction are properly reflected in the database or none are. Commit a transaction Rollback a transaction Consistency. Execution of a transaction in isolation preserves the consistency of the database. Isolation. Although multiple transactions may execute concurrently, each transaction must be unaware of other concurrently executing transactions. Intermediate transaction results must be hidden from other concurrently executed transactions. Durability. After a transaction completes successfully, the changes it has made to the database persist, even if there are system failures. Example of Fund Transfer Transaction to transfer $50 from account A to account B: 1. read(A) 2. A := A – 50 3. write(A) 4. read(B) 5. B := B + 50 6. write(B) Consistency requirement – the sum of A and B is unchanged by the execution of the transaction. Atomicity requirement — if the transaction fails after step 3 and before step 6, the system should ensure that its updates are not reflected in the database, else an inconsistency will result. Failure could be due to software or hardware Example of Fund Transfer (Cont.) Durability requirement — once the user has been notified that the transaction