May 7, 2010 at 3:47 am
I was facing some serious deadlock issues in a high transaction table.
For some select statement i have nolock .
But for few i can not put nolock, as i need accurate data.
this select statement becomes a deadlock victim at times.
can someone throw some light on this please ?
May 7, 2010 at 4:27 am
You shouldn't be using nolock anyway, not as a 'default' solution. It has side-effects. http://sqlblog.com/blogs/andrew_kelly/archive/2009/04/10/how-dirty-are-your-reads.aspx
Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.
DBCC TRACEON(1222,-1)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply