February 11, 2010 at 12:20 am
we are running the job in a production server that will send a mail message every half an hour till working now the job is failed
i checked in the job hystory
error is showing like:
Transaction (Process ID 30) was deadlocked on {lock} resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [SQLSTATE 40001] (Error 1205). The step failed.
please reply to resolve this issue .
Thanks in advance
February 11, 2010 at 12:42 am
You need to figure out what is actually involved and causing the deadlock.
How To ?
This will enable deadlock info printing in your sqlserver errorlog file.
dbcc traceon(1204, 1205, 3605, -1)
This will disable the trace.
dbcc traceoff(1204, 1205, 3605, -1)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 11, 2010 at 1:28 am
You don't need to enable traceflag 3605.
1204 writes the deadlock graph into the error log
1205 writes some of the deadlock search info into the error log.
3605 redirects some output (like that of DBCC PAGE) to the error log. It has no effect on deadlock graphs
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 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply