We have been tracking the deadlocks in our Dynamics SQL Server using Redgate SQL Monitor and basically 90% of our deadlocks happen because of this "DMG_UpdateInventory_ComputerName" stored procedure, which I believe is a Dynamics default store procedure.

We have also noticed that usually it's related to the table "ItemSite" and to the index "ItemSite0".

Has anyone else already had this kind of issues with this stored procedure on Dynamics SL 2015 and SQL Server 2016?


Leandro Perondi