General information about excessive locks

Best practices

1. Design errors made when you select and develop metadata object structure to implement applied functionality can lead to a great number of excessive locks and considerable decrease in system performance.  

Waiting upon data lock occurs when two different sessions of 1C:Enterprise attempt to capture the same resource. When different resources are used, there is no waiting upon lock. In this context, a "resource" is an undivided data set locked or not locked entirely.

It is important which resources are captured upon making actions with data. $$$ 

When you analyze metadata structure, pay attention to the following objects:

• Sequence
• Accounting registers
• Accumulation registers

See also:

• Locking reading of balance at the beginning of transactions
• Managed lock mode
• Inconsistency of indexes and query conditions
• Dereferencing reference fields of a composite type in the query language
• Queries joined with nested queries or virtual tables
• Using nested queries in join conditions
• Filtering virtual tables without using parameters
• Restrictions on the use of logical OR in query conditions