About database locks
Locking controls access to the same data at the same time by multiple users. To protect a transaction from another transaction modifying the same data, the first transaction puts a lock on the data. The lock remains until the transaction is done.
When a database lock occurs, concurrent transactions are limited in their access to the affected data resource. The limit is determined by the locking mode set by SQL Server. In the client, depending on the locking mode, users may be blocked from completing transactions on the locked data. If so, they'll typically get a message that indicates a lock condition.
Learn more about database locks in SQL Server in Transaction Locking and Row Versioning Guide.
View database locks
To view database locks, open the Database Locks page, which has the ID 9511, in the client.
The Database Locks page gives a snapshot of database lock requests for the current database. Intent and schema locks are excluded. It provides information like the table and database resource affected by the lock. It also shows the AL object or method associated with the lock, when that information is available. These details can help you better understand the locking condition. For an explanation about the fields shown, use the tooltips on the page. Learn more about the underlying lock information in sys.dm_tran_locks (Transact-SQL).
Tip
If you are running Business Central Fall 2018 or earlier, you'll have to use the Dynamics NAV Development Environment. On the Tools menu, choose Debugger, and then choose Database Locks.