If concurrent transactions wants to access different rows of the
same table then you should use
lock
Answers
Answered by
13
Explanation:
The ____ lock allows concurrent transactions to access the same row as long as they require the use of different fields within that row. Explanation: Lock is limited to the attributes of the relation
Answered by
0
Answer:
When there are multiple concurrent transactions, each operating on a different row of the same table, row-level locking is preferred.
Explanation:
What is Row-level locking?
- Row-level locking ensures that only the row accessed by an application is locked. As a result, all other rows on the same page are free and can be used by other applications. The Database Engine can also lock the page where the locked row is stored.
- If the WHERE clause of a statement cannot use an index, row-level locking systems can lock entire tables. UPDATES that cannot use an index, for example, lock the entire table. If a large number of single-row locks would be less efficient than a single table-level lock, row-level locking systems can lock entire tables.
- Row level locking is used by the database automatically when one transaction holds a lock on a row, and other transactions must wait for the acquired row level lock until the first transaction commits.
To learn more about locking refer to :
https://brainly.in/question/7487007
https://brainly.in/question/5367140
#SPJ2
Similar questions