| title |
Locks Event Category |
| description |
Locks Event Category |
| author |
WilliamDAssafMSFT |
| ms.author |
wiassaf |
| ms.date |
03/14/2017 |
| ms.service |
sql |
| ms.subservice |
supportability |
| ms.topic |
reference |
| ms.custom |
|
| 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 |
|
| monikerRange |
=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric-sqldb |
[!INCLUDE sqlserver2016-asdb-asdbmi-fabricsqldb]
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.