Zurück
-
Titel
Deadlock query using extended events uses a lot of CPU resources on SQL Server host -
Beschreibung
The extended events deadlock query can be a high consuming query on the SQL Server host that runs frequency and is listed in the top consuming list. Each execution is 11-25 seconds in duration and consumes CPU. -
Lösung
WORKAROUND 1
Change "Deadlock working mode" to Trace to use the old SQL Server trace method to collect deadlock details.
WORKAROUND 2
Move the old system_health*.xel files from SQL Server Log folder (e.g. "C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log") to another folder.
A file is use cannot be moved.WORKAROUND 3Please contact Support for Hotfix for this issue.STATUSThis issue has been logged as defect FOM-1060 and has been fixed in the 5.9.7.20 and higher releases of the SQL Server cartridge. -
Fehler-ID
FOM-1060