Handling DB Deadlocks

Question

How to handle database deadlocks in multi user environment.

I am getting this following error quite often with incomplete DB operations.

"Transaction (Process ID 119) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction"

Will the NOLOCK or ROWLOCK will solve this?

Afzaal Ahmad Zeeshan · Answer

Locks are the reason why deadlocks occur. Locking the items and records even further down is only going to make things worse. There can only be one solution that you review the SQL code and understand why this is happening where are the transactions being locked. Typically SQL Server itself prevents the locks from occurring but if they are it means that the code is problematic. Review the code and make try to execute it into small chunks bring it down to a smaller level; atomicity. Hopefully that would be able to solve it. Secondly will you be able to share the SQL code so that we can understand more on this?