Machine-translated by Google. Questions are authored in English.
Top

Discussion

With this type of SQL Server cursor concurrency no lock is obtained until the user updates the data.

  • A.READ_ONLY
  • B.SCROLL_LOCK
  • C.OPTIMISTIC
  • D.PESSIMISTIC

Answer: C

Correct answer: OPTIMISTIC

Optimistic concurrency takes no lock while the row is read and merely checks at update time whether the row has changed since. If it has, the update fails and the application must decide what to do. It assumes conflict is rare, which is what makes it faster than holding a lock through the whole read.

No comment is present. Be the first to comment.
Loading…

Post your comment

Please log in or register to post a comment.