150 likes | 275 Views
Transactions. Introduction. Transactions. Motivated by two independent requirements Concurrent database access Resilience to system failures. Transactions. Concurrent Database Access. Even more software. Select… Update… Create Table… Drop Index… Help… Delete…. More software.
E N D
Transactions Introduction
Transactions Motivated by two independent requirements • Concurrent database access • Resilience to system failures
Transactions Concurrent Database Access Even more software Select… Update… Create Table… Drop Index… Help… Delete… More software DBMS Data
Transactions Concurrent Access: Attribute-level Inconsistency UpdateCollegeSetenrollment=enrollment+1000 WherecName=‘Stanford’ concurrent with … UpdateCollegeSetenrollment=enrollment+1500 WherecName=‘Stanford’
Transactions Concurrent Access: Tuple-level Inconsistency UpdateApplySetmajor=‘CS’WheresID=123 concurrent with … UpdateApplySetdecision=‘Y’WheresID=123
Transactions Concurrent Access: Table-level Inconsistency UpdateApplySetdecision=‘Y’ WheresIDIn (Select sIDFrom Student Where GPA>3.9) concurrent with … UpdateStudentSetGPA=(1.1)GPAWheresizeHS>2500
Transactions Concurrent Access: Multi-statement inconsistency Insert Into Archive Select * From Apply Wheredecision=‘N’; • Delete From Apply Where decision=‘N’; concurrent with … Select Count(*)From Apply; Select Count(*) From Archive;
Transactions Concurrency Goal Execute sequence of SQL statements so they appear to be running in isolation • Simple solution: execute them in isolation But want to enable concurrency whenever safe to do so
Transactions Resilience to System Failures Bulk Load DBMS Data
Transactions Resilience to System Failures Insert Into Archive Select * From Apply Wheredecision=‘N’; • Delete From Apply Where decision=‘N’; DBMS Data
Transactions Resilience to System Failures Lots of updates buffered in memory DBMS Data
Transactions System-Failure Goal Guarantee all-or-nothing execution, regardless of failures DBMS Data
Transactions Solution for both concurrency and failures A transaction is a sequence of one or more SQL operations treated as a unit • Transactions appear to run in isolation • If the system fails, each transaction’s changes are reflected either entirely or not at all Transactions
Transactions Solution for both concurrency and failures A transaction is a sequence of one or more SQL operations treated as a unit. SQL standard: • Transaction begins automatically on first SQL statement • On “commit” transaction ends and new one begins • Current transaction ends on session termination • “Autocommit” turns each statement into transaction Transactions
Transactions Solution for both concurrency and failures A transaction is a sequence of one or more SQL operations treated as a unit Transactions