Nuestro buen amigo Andres Aguiar nos comparte su artículo:
Diego Vega wrote a very informative post that summarizes what you can do when you see deadlock errors in Entity Framework applications. They errors look like:
“Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.”
Even if Diego says that he did not hear about these issues often, I actually saw them quite often in two high-traffic EF applications where I was involved.
Most of the errors are get during reads, so the most likely cause is the one that Diego describes about having readers block readers, and handling the isolation levels in the way Diego suggest would solve it.
Fernando García Loera (Community Program Manager – Latin America Region)