Skip to content

Commit 6fd800e

Browse files
authored
Apply suggestions from PR review
Fix typo.
1 parent 5f30555 commit 6fd800e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/relational-databases/event-classes/lock-acquired-event-class.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ monikerRange: "=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-20
1616

1717
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
1818

19-
The Lock:Acquiredevent class indicates that acquisition of a lock on a resource, such as a data page, has been achieved.
19+
The Lock:Acquired event class indicates that acquisition of a lock on a resource, such as a data page, has been achieved.
2020

2121
The Lock:Acquired and Lock:Released event classes can be used to monitor when objects are being locked, the type of locks taken, and for how long the locks were retained. Locks retained for long periods of time might cause contention issues and should be investigated. For example, an application can be acquiring locks on rows in a table, and then waiting for user input. Because the user input can take a long time to occur, the locks can block other users. In this instance, the application should be redesigned to make lock requests only when needed and not require user input when locks have been acquired.
2222

0 commit comments

Comments
 (0)