Scribd Logo
Upload

Welcome to Scribd!

  • 7 views

    Concurrency Control

    Uploaded by

    Waleed Usman
    Concurrency control is a critical aspect of database management, ensuring that multiple transactions can execute concurrently without compromising data consistency. It involves techniques like locking, timestamping, and isolation levels to manage the simultaneous access and modification of data by multiple users or transactions. The goal is to maintain a balance between data integrity and system performance in a multi-user database environment.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Concurrency Control

    Uploaded by

    Waleed Usman
    7 views37 pages
    Concurrency control is a critical aspect of database management, ensuring that multiple transactions can execute concurrently without compromising data consistency. It involves techniques like locking, timestamping, and isolation levels to manage the simultaneous access and modification of data by multiple users or transactions. The goal is to maintain a balance between data integrity and system performance in a multi-user database environment.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Concurrency control is a critical aspect of database management, ensuring that multiple transactions can execute concurrently without compromising data consistency. It involves techniques like locking, timestamping, and isolation levels to manage the simultaneous access and modification of data by multiple users or transactions. The goal is to maintain a balance between data integrity and system performance in a multi-user database environment.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    7 views37 pages

    Concurrency Control

    Uploaded by

    Waleed Usman
    Concurrency control is a critical aspect of database management, ensuring that multiple transactions can execute concurrently without compromising data consistency. It involves techniques like locking, timestamping, and isolation levels to manage the simultaneous access and modification of data by multiple users or transactions. The goal is to maintain a balance between data integrity and system performance in a multi-user database environment.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 37

    Database Systems

    Week 11: Concurrency Control


    What is a Transaction?
    What is a Transaction?
    • Any action that reads from and/or writes to a database may consist of:
    • Simple SELECT statement to generate list of table contents
    • Series of related UPDATE statements to change values of attributes in various
    tables
    • Series of INSERT statements to add rows to one or more tables
    • Combination of SELECT, UPDATE, and INSERT statements (example: sale of 10
    units of product)
    What is a Transaction?
    • Transaction is logical unit of work that must be either entirely
    completed or aborted
    • Successful transaction changes database from one consistent state to
    another
    • One in which all data integrity constraints are satisfied
    • Most real-world database transactions are formed by two or more
    database requests
    • Equivalent of a single SQL statement in an application program or transaction
    Evaluating Transaction Results
    • Not all transactions update database
    • SQL code represents a transaction because database was accessed
    • Improper or incomplete transactions can have devastating effect on
    database integrity
    • Some DBMSs provide means by which user can define enforceable constraints
    (check constraints)
    • Other integrity rules are enforced automatically by the DBMS (record already
    exists)
    Evaluating Transaction Results

    Figure 9.2
    Transaction Properties
    • Atomicity - undividable
    • Requires that all operations (SQL requests) of a transaction be completed. if
    not, the transaction is aborted.
    • Consistency
    • Indicates the permanence of the database’s consistent state.
    • A transaction takes a database from one consistent state to another
    consistent state.
    • When a transaction is completed, the database must be in a consistent state;
    if any of the transaction parts violates an integrity constraint, the entire
    transaction is aborted.
    Transaction Properties
    • Isolation
    • Data used during execution of a transaction cannot be used by
    second transaction until first one is completed (useful in multi-user
    environment)
    • Durability
    • ensures that once transaction changes are done (committed), they cannot be
    undone or lost, even in the event of a system failure.
    Transaction Properties
    • Serializability– serial order (concurrency)
    • Ensures that concurrent execution of several transactions yields consistent
    results
    Transaction Management with SQL
    • ANSI has defined standards that govern SQL database transactions
    • Transaction support is provided by two SQL statements: COMMIT and
    ROLLBACK
    Transaction Management with SQL
    • ANSI standards require that, when a transaction sequence is initiated
    by a user or an application program, it must continue through all
    succeeding SQL statements until one of four events occurs
    • COMMIT statement is reached
    • ROLLBACK statement is reached
    • End of program is reached
    • Program is abnormally terminated
    The Transaction Log
    • Transaction log stores a record for the beginning of transaction
    • For each transaction component (SQL statement):
    • Type of operation being performed (update, delete, insert)
    • Names of objects affected by transaction
    • “Before” and “after” values for updated fields
    • Pointers to previous and next transaction log entries for the same transaction
    The Transaction Log
    • Transaction log stores an ending (COMMIT) of the transaction
    • Transaction log is Used for recovery from rollback, abnormal
    termination, system failure (such as, disk crash).
    The Transaction Log

    Concurrency Control and Database backup and recovery


    Concurrency Control
    • Coordination of simultaneous transaction execution in a
    multiprocessing database system
    • Objective is to ensure serializability of transactions in a multiuser
    database environment
    Concurrency Control
    • Simultaneous execution of transactions over a shared database can
    create several data integrity and consistency problems:
    • Lost updates
    • Uncommitted data
    • Inconsistent retrievals
    Lost Updates
    Assume that you have a product whose current PROD_QOH value is 35
    Lost Updates
    Assume that you have a product whose current PROD_QOH value is 35
    Lost Updates
    Suppose that a transaction is able to read a product’s PROD_QOH value from the table
    before a previous transaction (using the same product) has been committed
    Uncommitted Data
    The phenomenon of uncommitted data occurs when two transactions, T1 and T2, are
    executed concurrently and the first transaction (T1) is rolled back after the second
    transaction (T2) has already accessed the uncommitted data—thus violating the
    isolation property of transactions. T1 is forced to roll back due to an error during the
    update of the invoice total; hence, it rolls back all the way, undoing the inventory
    update
    Uncommitted Data
    Uncommitted Data
    Inconsistent Retrievals
    Inconsistent retrievals occur when a transaction accesses data before and after
    another transaction(s) finish working with such data.
    Inconsistent Retrievals
    Inconsistent Retrievals
    The Scheduler
    • Special DBMS program
    • Purpose is to establish order of operations within which concurrent
    transactions are executed
    • Interleaves execution of database operations to ensure serializability
    and isolation of transactions
    The Scheduler
    • Bases its actions on concurrency control algorithms, like locking and
    time stamping.
    • Ensures computer’s central processing unit (CPU) is used efficiently,
    not based on FCFS
    • With FCFS CPU waits for read and write operation to finish.
    • Facilitates data isolation to ensure that two transactions do not
    update same data element at same time
    The Scheduler
    Concurrency Control with Locking Methods
    • Lock
    • Guarantees exclusive use of a data item to a current transaction
    • Required to prevent another transaction from reading inconsistent data
    • Lock manager
    • Responsible for assigning and policing the locks used by transactions
    Lock Granularity
    • Indicates level of lock use
    • Locking can take place at following levels:
    • Database
    • Table
    • Page
    • Row
    • Field (attribute)
    Lock Granularity
    • Database-level lock
    • Entire database is locked (good for batch not for multi-user DB)
    • Table-level lock
    • Entire table is locked
    • Page-level lock
    • Entire diskpage is locked
    • The most frequently used method
    Lock Granularity
    • Row-level lock
    • Allows concurrent transactions to access different rows of same
    table, even if rows are located on same page. It creates
    overhead
    • Field-level lock
    • Allows concurrent transactions to access same row, as long as
    they require use of different fields (attributes) within that row
    • Rarely done. It creates highest overhead
    Lock Granularity
    Lock Granularity
    Lock Granularity
    Lock Granularity

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy