When the system was tested, due to the use of automated test scripts to run, all of a sudden a lot of sqlserver deadlock problems.
We are in the system test phase, and where there is time to carefully analyze how these are out of the deadlock, directly on the retry it.
In the process of change in sql, sql found written in really varied ah, that chaos ah.
And consequently do not say it, unified interface direct calls it, took about two weeks, the buzz of all these sql call to unity in a class, then you only need to process much simpler deadlock in this class, and then retry on the line, but it seems still remember a few bug, and there is a related transaction, but also realize that after a deadlock, transaction also need a new one.
Many bug not to modify, simply do not know how it is, do not know how the future improvements.
So do not always complain about the opportunity in change bug, not everyone has such a.
Opportunities always come to fight.