December 15, 2008 at 1:50 pm
I'll start off with stating that I know that there is a difference between Database Transaction Blocking and failure to communicate with the Database Engine. However, this is kind of strange occupance.
I have this application that has a three tiered architecture, Database, Process/Service, and Client. The Service layer communicates with the Database and deals with much of the business logic of inserts/deletes etc. and the Service maintains a log of errors and such that it encounters when dealing with the database.
In the log file I am seeing a large number of deadlocks occurring more and more frequently. The messages look like this:
"[0x8004F100][61184] [40001](1205)[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 96) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."
This might happen one or two times in a minute and then subside or it can occur multiple times for several minutes. In nearly ever case that I have traced thus far, the deadlock has occurred on select statements. As I said this has been increasing in frequency on the Database and I think that it might be due in part to statements taking a long time due to fragmented indexes and statistics. I'm going to work on that next.
Anyway, back to my point. In a few instances there are many of the deadlock messages followed by what I simply call a General Network Error. Here's that message:
][0x8004F100][61184] [01000](10054)[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()). [08S01](11)[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
I know the obvious question, "Is there a problem with the network?". In a word, I don't think that's it. The key reason is because the Service that is logging the message is on the same Server as the Database, more or less eliminating your typical networking from the equation.
Really, any ideas anyone has would be appreciated. I'm going to dig into stats and such to see what I come up with there.
Regards, Irish
July 16, 2015 at 8:52 am
I think I am experiencing the same issue at the minute, however I am not getting the deadlock message, just the General Network error. It happen predominately on a remote site across VPN and is intermittent, and is only caused by select queries that have a join or query with multiple result sets. Simple select queries continue to work fine and a computer restart is required to get queries running again okay. I am currently trying to add WITH (NO LOCK) to joined tables to see if it makes a difference.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply