1 Transactions Serializability Isolation Levels Atomicity

2 The Setting uDatabase systems are normally being accessed by many users or processes at the same time. wBoth queries and modifications. uUnlike operating systems, which support interaction of processes, a DMBS needs to keep processes from troublesome interactions.

3 Example: Bad Interaction uYou and your domestic partner each take $100 from different ATM’s at about the same time. wThe DBMS better make sure one account deduction doesn’t get lost. uCompare: An OS allows two people to edit a document at the same time. If both write, one’s changes get lost.

4 Transaction in SQL Example) Think that chooseSeat() program in embedded SQL(C host language ) Input : flight number, date, seat number Output : reservation seat if it possible EXEC SQL BEGIN DECLARE SECTION int flight; char date[10]; char seat[3]; int occ; EXEC SQL END DECLARE SECTION;

5 Void chooseSeat() { /* entered flight Number, date, seat number */ EXEC SQL SELECT occupied INTO :occ FROM Flights WHERE fltNum = :flight AND fltDate = :date AND fltSeat = :seat; if ( !occ ) { EXEC SQL UPDATE Flights SET occupied = TRUE WHERE fltNum = :flight AND fltDate = :date AND fltSeat = :seat; /* notify to user that the reservation is success */ } else /* notify to user that the seat not available */ } User1 found that 7A is available time Transaction in SQL T1: User1(7A)T2: User2 (7A) User2 found that 7A is available User2 reserved 7A and changed TRUE(7A) User2 reserved 7A and changed TRUE(7A) 7A reserved by user1(T1) and user2(T2) concurrently 7A reserved by user1(T1) and user2(T2) concurrently

6 Transaction in SQL void transfer() { /* enter account 1 and 2 and amount of money to transfer */ EXEC SQL SELECT balance INTO :balance1 FROM Accounts WHERE acctNo = :acct1; if (balance1 >= amount) { EXEC SQL UPDATE Accounts SET balance = balance + :amount WHERE acctNo = :acct2; EXEC SQL UPDATE Accounts SET balance = balance - :amount WHERE acctNo = :acct1; } else /* print a error message that there were insufficient funds */ } Happened System Failure (power off, disk error,..)

7 Transaction uA Transaction is a collection of one or more operations on the database that must be executed atomically, that is, either all operations are performed or none are.  Concurrency Control  Recovery

8 COMMIT uThe SQL statement COMMIT causes a transaction to complete. wIt’s database modifications are now permanent in the database.

9 ROLLBACK uThe SQL statement ROLLBACK also causes the transaction to end, but by aborting. wNo effects on the database. uFailures like division by 0 or a constraint violation can also cause rollback, even if the programmer does not request it.

10 Example - Transaction BEGIN_TRANS; UPDATE ACCOUNT SET Balance = Balance WHERE Accnt = 'A'; IF ERROR GO TO UNDO; UPDATE ACCOUNT SET Balance = Balance WHERE Accnt = 'B'; IF ERROR GO TO UNDO; COMMIT TRANS; GO TO FINISH; UNDO: ROLLBACK TRANS; FINISH: RETURN; END_TRANS Money Transfer A: = A -100  B:= B Money Transfer A: = A -100  B:= B TransactionTransaction

11 ACID Transactions uA DBMS is expected to support “ACID transactions,” processes that are: wAtomic : Either the whole process is done or none is. wConsistent : Database constraints are preserved. wIsolated : It appears to the user as if only one process executes at a time. wDurable : Effects of a process do not get lost if the system crashes.

12 Transactions in SQL uSQL supports transactions, often behind the scenes. wEach statement issued at the generic query interface is a transaction by itself. wIn programming interfaces like Embedded SQL or PSM, a transaction begins the first time a SQL statement is executed and ends with the program or an explicit transaction- end.

13 An Example: Interacting Processes uAssume the usual Sells(bar,beer,price) relation, and suppose that Joe’s Bar sells only Bud for $2.50 and Miller for $3.00. uSally is querying Sells for the highest and lowest price Joe charges. uJoe decides to stop selling Bud and Miller, but to sell only Heineken at $3.50.

14 Sally’s Program uSally executes the following two SQL statements, which we call (min) and (max), to help remember what they do. (max)SELECT MAX(price) FROM Sells WHERE bar = ’Joe’’s Bar’; (min)SELECT MIN(price) FROM Sells WHERE bar = ’Joe’’s Bar’;

15 Joe’s Program uAt about the same time, Joe executes the following steps, which have the mnemonic names (del) and (ins). (del) DELETE FROM Sells WHERE bar = ’Joe’’s Bar’; (ins) INSERT INTO Sells VALUES(’Joe’’s Bar’, ’Heineken’, 3.50);

16 Interleaving of Statements uAlthough (max) must come before (min), and (del) must come before (ins), there are no other constraints on the order of these statements, unless we group Sally’s and/or Joe’s statements into transactions.

17 Example: Strange Interleaving uSuppose the steps execute in the order (max)(del)(ins)(min). Joe’s Prices: Statement: Result: uSally sees MAX < MIN! 2.50, 3.00 (del) (ins) 3.50 (min) , 3.00 (max) 3.00

18 Fixing the Problem by Using Transactions uIf we group Sally’s statements (max)(min) into one transaction, then she cannot see this inconsistency. uShe sees Joe’s prices at some fixed time. wEither before or after he changes prices, or in the middle, but the MAX and MIN are computed from the same prices.

19 Another Problem: Rollback uSuppose Joe executes (del)(ins), not as a transaction, but after executing these statements, thinks better of it and issues a ROLLBACK statement. uIf Sally executes her statements after (ins) but before the rollback, she sees a value, 3.50, that never existed in the database.

20 Solution uIf Joe executes (del)(ins) as a transaction, its effect cannot be seen by others until the transaction executes COMMIT. wIf the transaction executes ROLLBACK instead, then its effects can never be seen.

21 Isolation Levels uSQL defines four isolation levels = choices about what interactions are allowed by transactions that execute at about the same time. uHow a DBMS implements these isolation levels is highly complex, and a typical DBMS provides its own options.

22 Choosing the Isolation Level uWithin a transaction, we can say: SET TRANSACTION ISOLATION LEVEL X where X = 1.SERIALIZABLE 2.REPEATABLE READ 3.READ COMMITTED 4.READ UNCOMMITTED

23 Serializable Transactions uIf Sally = (max)(min) and Joe = (del)(ins) are each transactions, and Sally runs with isolation level SERIALIZABLE, then she will see the database either before or after Joe runs, but not in the middle. uIt’s up to the DBMS vendor to figure out how to do that, e.g.: wTrue isolation in time. wKeep Joe’s old prices around to answer Sally’s queries.

24 Isolation Level Is Personal Choice uYour choice, e.g., run serializable, affects only how you see the database, not how others see it. uExample: If Joe Runs serializable, but Sally doesn’t, then Sally might see no prices for Joe’s Bar. wi.e., it looks to Sally as if she ran in the middle of Joe’s transaction.

25 Read-Commited Transactions uIf Sally runs with isolation level READ COMMITTED, then she can see only committed data, but not necessarily the same data each time. uExample: Under READ COMMITTED, the interleaving (max)(del)(ins)(min) is allowed, as long as Joe commits. wSally sees MAX < MIN.

26 Repeatable-Read Transactions uRequirement is like read-committed, plus: if data is read again, then everything seen the first time will be seen the second time. wBut the second and subsequent reads may see more tuples as well.

27 Example: Repeatable Read uSuppose Sally runs under REPEATABLE READ, and the order of execution is (max)(del)(ins)(min). w(max) sees prices 2.50 and w(min) can see 3.50, but must also see 2.50 and 3.00, because they were seen on the earlier read by (max).

28 Read Uncommitted uA transaction running under READ UNCOMMITTED can see data in the database, even if it was written by a transaction that has not committed (and may never). uExample: If Sally runs under READ UNCOMMITTED, she could see a price 3.50 even if Joe later aborts.