Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
abhi4u86
Starting Member
4 Posts |
 Posted - 2009-05-11 : 08:50:17
|
| Hi all, Please let me know if we have any alternative to remove deadlock apart from killing the blocking process.regards,Abhishek |
|
|
NeilG
Aged Yak Warrior
530 Posts |
Posted - 2009-05-11 : 09:04:46
|
| Don't think there is, I believe that kill or using Activity monitor to kill the process are the only two ways |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-05-11 : 22:29:22
|
| Yes,1)Allow Apps to access objects in same order.2)Implement indexes.3)Use low isolation level.4) Take advantage of normalization. |
|
|
|
nwalter
Starting Member
39 Posts |
Posted - 2009-05-19 : 00:13:31
|
| It's also not a deadlock, it's just blocking. Deadlocks, by definition, are automatically detected and resolved by SQL server, deadlocks are actually not nearly as bad as blocking. For fixing blocking, SQL server does not have any method of killing just a single transaction by a user or process without killing the whole process. Your best bet is to narrow down what is actually causing the blocking in the first place.You either have a very long running process with a high isolation level taking a lock on an entire table or even higher, or you have an app that is misbehaving and opening a transaction without ever commiting it. Bottom line is, fix the app not the SQL server as SQL is only doing what your app is telling it to do. |
|
|
|
|
|
|
do we have any alternative to remove deadlock