February 22, 2009 at 11:28 pm
Error Details : System.Data.SqlClient.SqlException: Transaction (Process ID 59) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at ReportScreen.ShowVerkoopbonReport()
how to resolve this?
The application is live at production server.
February 22, 2009 at 11:35 pm
Hi
The error message shows that there was a deadlock and transaction id (spid) 59 was killed by sql server to resolve the deadlock.
You need to traceout where/why the deadlock is happening and then resolve it. There are lots of articles in this site and on the web for this. Go through some of them and give it a try.
"Keep Trying"
February 23, 2009 at 12:51 am
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
February 23, 2009 at 1:34 am
hey Guys
thanx for your posts.
GilaMonster, I will pass the statement to the production people to get the graph u described. I will come back very shortly.
Tracing is really not adaptable in my case because the application is live and turning on the tracing might slow down the application. The production people will not allow it.
I m wanting some kind of solution which can prevent such kind of situation and user does not come to know anything like that hpnd.
I heard abt row versionising by Read_commited stmts.
Should I use it?
February 23, 2009 at 7:12 am
ushasheokand (2/23/2009)
Tracing is really not adaptable in my case because the application is live and turning on the tracing might slow down the application. The production people will not allow it.
Server-side traces have very little impact when done properly.
I m wanting some kind of solution which can prevent such kind of situation and user does not come to know anything like that hpnd.
Without seeing the graph, no idea.
I heard abt row versionising by Read_commited stmts.
Should I use it?
Maybe. Maybe not. Need more information.
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 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply