which of the following best describes why table locking is often not desirable compared to page or row locking?

Question

Options

• ATable locks can have deadlocks.
• BTable locks create concurrency issues.
• CTable locks prevent other clients from making any changes to the table until released.
• DTable locks can cause data corruption issues if more than one client tries to make changes while

• A
  8% (2)
• B
  73% (19)
• C
  4% (1)
• D
  15% (4)

Explanation

Table locking is not as desirable as page or row locking for concurrency in a mixed read/write A table lock prevents other clients from making any changes to the table, even if the client that holds the lock is not accessing the parts of the table that other clients want to modify. With page and row locks, a client that locks a page or row does not prevent changes by other clients to other pages or rows. Deadlock cannot occur with table locking as it can with page or row locking.

No community discussion yet for this question.