From what I understand, a deadlock is normally something special where 2 things wait for each other in a circle with no way out. Isn't a deadlock different from a regular lock? If all NetXMS is doing is just deletes and some inserts, I would maybe expect some regular locks/waits, but they resolve themselves given enough time. So most things just poll every minute and retain for 90 days. SELECT polling_interval, retention_time, count(polling_interval) FROM items GROUP BY polling_interval, retention_time ORDER BY retention_time, polling_interval It also provides with a truncated SQL statement.
The deadlock graph shows me the Objectid and Object name of the underlying object. I have an application running against a SQL Server 2016 database that is causing deadlocks.
#Sql server deadlock count full
SELECT var_name, var_value FROM config WHERE var_name like 'DefaultDCI%' Deadlocks - Finding full SQL statement from deadlock report. It's not doing anything other than NetXMS and SQL. The system isn't anything special, but not completely bad: Dell R420, Dual E5-2430 2.2GHz, 32GB Ram, 2x 1TB drive in RAID1. This doesn't happen every night, and the number of deadlocks isn't the same every time, but it's often enough that it's waking people up at 2am.Īnyone have any thoughts on where to go to troubleshoot? " Transaction (Process ID 63) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. We also see some of the DELETE statements from the housekeeper failing for similar reasons: "SQL query failed (Query = "DELETE FROM idata_2637 WHERE (item_id=1817 AND idata_timestamp<1583907634) OR. SQL query failed (Query = "INSERT INTO idata_2301 (item_id,idata_timestamp,idata_value,raw_value) VALUES (1061,1591683195,'Ok','3')"): Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Many nights at 2am, when the housekeeper runs, we get a few deadlocks on SQL Server.
0 kommentar(er)
