1. ACS - 3902 R McFadyen 1 Transaction A transaction is an atomic unit of work that is either completed in its entirety or not done at all. For recovery purposes, the system needs to keep track of when the transaction starts, terminates, and commits or aborts.

2. ACS - 3902 R McFadyen 2 ACID properties Atomicity: A transaction is an atomic unit of processing; it is either performed in its entirety or not performed at all. Consistency preservation: A correct execution of the transaction must take the database from one consistent state to another. Isolation: A transaction should not make its updates visible to other transactions until it is committed. Durability or permanency: Once a transaction changes the database and the changes are committed, these changes must never be lost because of subsequent failure.

3. ACS - 3902 R McFadyen 3 Transaction and System Concepts Transaction operations: 1. begin_transaction: This marks the beginning of transaction execution. 2. read or write: These specify read or write operations on the database items that are executed as part of a transaction. i.e. SELECT, UPDATE, INSERT, DELETE Two ways for a transaction to end: 3. commit_transaction: This signals a successful end of the transaction so that any changes (updates) executed by the transaction can be safely committed to the database and will not be undone. 4. rollback (or abort): This signals that the transaction has ended unsuccessfully, so that any changes or effects that the transaction may have applied to the database are undone.

4. ACS - 3902 R McFadyen 4 Transaction and System Concepts Example This transaction makes two updates, but then rolls back and so it is as if it never even started: Begin Transaction; Update employees set salary=1000000 where employeeid=7; Update employees set salary=salary+100 where employeeid=5; Rollback; In the absence of Begin Transaction, each statement will be treated as a transaction that is automatically committed