My SQL Server jobs fail with a "Transaction (Process ID XX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim." error, how should I investigate ?
Best Answer
S
Stéphanie FOURRIER
said
over 2 years ago
You should first check what queries are involved in the deadlock :
According to the result of the appropriate query, you should be able to understand if the deadlock occurs :
Because of an external process than xDM (for example, viewing tables in some query tools lock the tables...) => analyze if this other process is expected and fix it by updating it or killing it (spwho to identify the process and kill <processid>).
Because of an internal xDM query
Check that your Data Location and Repository schemas follow our Installation Guide about the READ_COMMITTED_SNAPSHOT option that should be turned on. This can be verified by running this query : select name, is_read_committed_snapshot_on from sys.databases;
Check that you don't have defined many different Job Queues for the same entity
If you are using Continuous Loads with large datasets, you might hit the fixed bug MDM-10837 (see the release notes). Upgrading to a higher version than 5.2.4 might solve your issue.
According to the result of the appropriate query, you should be able to understand if the deadlock occurs :
Because of an external process than xDM (for example, viewing tables in some query tools lock the tables...) => analyze if this other process is expected and fix it by updating it or killing it (spwho to identify the process and kill <processid>).
Because of an internal xDM query
Check that your Data Location and Repository schemas follow our Installation Guide about the READ_COMMITTED_SNAPSHOT option that should be turned on. This can be verified by running this query : select name, is_read_committed_snapshot_on from sys.databases;
Check that you don't have defined many different Job Queues for the same entity
If you are using Continuous Loads with large datasets, you might hit the fixed bug MDM-10837 (see the release notes). Upgrading to a higher version than 5.2.4 might solve your issue.
S
Sneha Jadala
said
about 2 years ago
Hi,
When I tried above queries, sp_who2, there was none in blk_by column and other query please see below screenshot-
Stéphanie FOURRIER
My SQL Server jobs fail with a "Transaction (Process ID XX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim." error, how should I investigate ?
You should first check what queries are involved in the deadlock :
According to the result of the appropriate query, you should be able to understand if the deadlock occurs :
spwho
to identify the process andkill <processid>
).select name, is_read_committed_snapshot_on
from sys.databases;
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstStéphanie FOURRIER
You should first check what queries are involved in the deadlock :
According to the result of the appropriate query, you should be able to understand if the deadlock occurs :
spwho
to identify the process andkill <processid>
).select name, is_read_committed_snapshot_on
from sys.databases;
Sneha Jadala
Hi,
When I tried above queries, sp_who2, there was none in blk_by column and other query please see below screenshot-
Thanks,
Sneha
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 43 topics