| title |
Locks Event Category | Microsoft Docs |
| ms.custom |
|
| ms.date |
03/14/2017 |
| ms.prod |
sql |
| ms.reviewer |
|
| ms.technology |
supportability |
| ms.topic |
conceptual |
| helpviewer_keywords |
Locks event category [SQL Server] |
SQL Server event classes, Locks event category |
event classes [SQL Server], Locks event category |
lock escalation [SQL Server], locks event category |
|
| ms.assetid |
27d6afa2-7dab-4fe7-a1ad-064b879dc654 |
| author |
stevestein |
| ms.author |
sstein |
| monikerRange |
=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
Use the event classes in the Locks event category to monitor locking activity in an instance of the [!INCLUDEmsCoName] [!INCLUDEssDEnoversion]. These event classes can help you investigate locking problems caused by multiple users reading and modifying data concurrently.
Because the [!INCLUDEssDE] often processes many locks, capturing the Locks event classes during a trace can incur significant overhead and result in large trace files or tables.