Pessimistic Concurrency Control

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

This section provides details about the pessimistic concurrency control which can be achieved with Telerik Data Access.

Pessimistic concurrency control can be implemented by providing a restrictive isolation level for the transactions issued against the database. This allows the operations in their scope to be executed independently from the operations in concurrent transactions which might be running at the time present. This type of concurrency control is related to certain problems, which are acceptable for some applications, as either they can handle them or an occurrence of such anomalies does not strongly influence the application's purpose.

Telerik Data Access allows you to implement pessimistic concurrency control by setting the isolation level of each transaction started with an instance of the context. The How to: Set Isolation Level article will provide you with an example that demonstrates the workflow.