Resolving deadlocks with SQL Server performance monitoring DBAs must know immediately when one occurs, by alerting on 1205 errors, and then need at their fingertips all of the information necessary to troubleshoot the deadlock and ensure that it doesn't recur.

Nevertheless, deadlock errors cause resource contention, disruption and delay, and cannot be ignored. It should also have retry logic that allows the victim transaction to rerun, once the deadlock clears. Any application code that issues database queries should be equipped with error handling that deals with the problem gracefully, and sends the calling client a 'user friendly' message. Ideally, no user should ever be confronted with error message 1205, even if a deadlock does occur. It means that the other sessions may proceed, but that is little comfort to the hapless victim, and if that victim happens to be a session running a critical business process, then it may soon be of little comfort to the DBA. It automatically chooses one of the sessions as the 'victim', kills it and rolls back its transaction. The result is a 'circular chain' where no session can complete, and so SQL Server is forced to intervene to clear up the mess. Two or more sessions were waiting to acquire a lock on a resource already locked by another session in the same locking chain.

Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. What are SQL Server Deadlocks & How Do You Fix Them | Redgate

Project red buffer gate