J
James Cates
Guest
We're experiencing intermittent deadlocks with triggers when calling update or insert procedures from a .Net application. Now, previous developers created a "retry" method, which retries 5 times using a sleep of 5 seconds between tries, but this is often enough exceeded that users are complaining. I don't like trying to solve issues like this in the code, I would rather do it at the db or data layer level. Ideas? Best practices for this type of problem?
Continue reading...
Continue reading...