RE: Transaction (Process ID 65) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.

2013-03-19 Thread Greg Low (GregLow.com)
PM To: ozDotNet Subject: Re: Transaction (Process ID 65) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. I use SQL Profiler to investigate deadlocks. See this article: Analyse Deadlocks with SQL Server

Re: Transaction (Process ID 65) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.

2013-03-18 Thread Tony Wright
I use SQL Profiler to investigate deadlocks. See this article: Analyse Deadlocks with SQL Server Profiler. http://msdn.microsoft.com/en-us/library/ms188246.aspx On Tue, Mar 19, 2013 at 3:14 PM, Corneliu I. Tusnea wrote: > Hi, > > I have a SQL Procedure that call a SQL Function that (way too ofte