Answer: First, note these Oracle lock scripts and Oracle deadlocks.
Every time you make a change to a table, My SQL must eventually commit that change to disk.
To understand better the locking in SQL Server, it is important to understand that locking is designed to ensure the integrity of the data in the database, as it forces every SQL Server transaction to pass the ACID test.
ACID test consists of 4 requirements that every transaction have to pass successfully: SQL Server locking is the essential part of the isolation requirement and it serves to lock the objects affected by a transaction.
Essentially, locks are in-memory structures which have owners, types, and the hash of the resource that it should protect.
A lock as an in-memory structure is 96 bytes in size.