The correct answer is A. Granularity.
Locking granularity is the level of detail at which locks are placed on data in a database. The three main levels of locking granularity are row, page, and table.
- Row locking is the most granular level of locking. A row lock is placed on a single row of data. This type of locking is typically used for transactions that need to update or delete a single row of data.
- Page locking is a coarser level of locking than row locking. A page lock is placed on an entire page of data. This type of locking is typically used for transactions that need to update or delete multiple rows of data that are located on the same page.
- Table locking is the coarsest level of locking. A table lock is placed on an entire table of data. This type of locking is typically used for transactions that need to update or delete all of the data in a table.
The level of locking granularity that is used depends on the type of transaction that is being performed. For example, a transaction that needs to update a single row of data would use row locking, while a transaction that needs to update all of the data in a table would use table locking.
The choice of locking granularity can have a significant impact on the performance of a database. Fine-grained locking (row locking) can improve performance by reducing the number of locks that are placed on data. However, fine-grained locking can also increase the risk of deadlocks. Coarse-grained locking (page locking or table locking) can reduce the risk of deadlocks, but it can also reduce performance by increasing the number of locks that are placed on data.
The choice of locking granularity is a trade-off between performance and risk. The appropriate level of locking granularity for a particular database depends on the specific needs of the application that is using the database.
