Reputation: 460238
i have logged an exception thrown by an ASP.NET-Application.
Message: Transaction (Process ID 56) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
I'm sure that the reason for it was, that i was running some selects
directly in SSMS on tables that were queried in the application in the same time.
So now my question is:
Thank you in advance.
Upvotes: 4
Views: 6562
Reputation: 432541
SET DEADLOCK_PRIORITY allows you to fine tune the precedence
You can specify this in your SSMS session (per query window) or globally:
Upvotes: 5