The Microsoft SQL Server default isolation level is Read Committed. You may want to consult with your developers to determine what transaction isolation level that are in use. This is really more of a development issue. If anyone has any suggestions as to something we can do I will buy them multiple pints. When we moved the db to the new box it was backed up from the old and restored to the new. Some of the major tables are way too wide and have a stupid amount of triggers on, but there is nothing we can do about this now.Ī lot of the pids seem to be the same for the same users who are trying multiple times.Įrror Message: Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. We have checked all the indexes and they are as good as they can be right now. net app used by a couple of hundred people or so is generating a huge amount of deadlocks and timeouts on the SQL box and we are struggling to work out why. Our old sql box had problems but nothing like what we are experiencing with the new one, although on the day of rolling out it was running super fast, within a week it's a complete mess. We have recently updated our sql box with a complete monster, with loads of cores and ram, however we are stuck with our old DB schema which is crapola. Looks like today is going to be another rubbish one.
0 kommentar(er)
