UNIT V- TRANSACTION MANAGEMENT

1)TRANSACTION Every user program in Database will Execute as a transaction, which is a collection of read and write operations. The relation or pages, records on which we are performing read and write operations is called a database object. 1) For reading a data object first we have to bring its value from disk to memory and then from memory to program 2) For Writing first the data object should be modified in memory then this update should write to disk. Every transaction will contain four important properties 1. User should execute a transaction always as an Atomic unit .i.e either all actions of a transaction should complete or none of them should not complete 2. Every transaction run by the user should kept the database in a Consistent state. It is responsibility of user to maintain database consistency. 3. Even though DBMS running multiple transactions concurrently, each one should look like an individual unit. This property of a transaction is called Isolation. 4. Once the transaction was successfully completed all it changes should reflect in disk in order to persist when system crash occurs. this is called Durability. These four properties of transaction are called as ACID properties. Consistency & Isolation Users are responsible for ensuring transaction consistency. For example, the user may (naturally!) have the consistency criterion that fund transfers between bank accounts should not change the total amount of money in the accounts. That is even though deducting funds from one transaction will left database temporarily inconsistent the total amount before the transaction and after the transaction commits should be same.