Dynamics 365 Business Central, Azure SQL and Optimized Locking

Optimized locking is a new Azure SQL database engine feature recently announced that drastically reduces lock memory and the number of locks concurrently required for writes. Optimized locking helps on reducing lock memory as very few locks are held for large transactions. In addition, optimized locking also avoids lock escalations and this allows more concurrent access to the same table.

Optimized locking uses two primary components: Transaction ID (TID) locking (also used in other row versioning features) and lock after qualification (LAQ). It does not require any additional configuration. For more details:

• A transaction ID (TID) is a unique identifier of a transaction. Each row is labeled with the last TID that modified it. Instead of potentially many key or row identifier locks, a single lock on the TID is used.

• Lock after qualification (LAQ) is an optimization that evaluates predicates of a query on the latest committed version of the row without acquiring a lock, thus improving concurrency.

Dynamics 365 Business Central, Azure SQL and Optimized Locking – Stefano Demiliani

More about Dynamics 365 Business Central

Dynamics 365 Business Central is a cloud-based ERP solution that helps small and medium businesses manage their finances, operations, sales, customer service and more. It can be easily integrated with other applications such as Azure SQL for data storage and optimized locking to ensure data integrity.

With Dynamics 365 Business Central, users can access real-time insights into their business performance via the web or mobile device. Additionally, it provides advanced capabilities like predictive analytics to support better decision making. Furthermore, Dynamics 365 Business Central offers enhanced security features like user authentication and role-based access control so users have peace of mind when using the system.