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 |
|
anilinsqlteam
Starting Member
9 Posts |
Posted - 2006-10-12 : 23:06:49
|
| Is there any chance that the deadlock will break the database connection.And if yes how to protect the conncetion that should not affect by deadlock.RegardsAnil |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-10-13 : 00:15:13
|
a deadlock is a deadlock, unless you have an application running those transactions with a session time limit, then they stay that way until you kill the offending process id in sql or disconnect from the appsI don't think you'd want to protect a connection from getting affected by a deadlock, the deadlock should affect the connection so you don't get hanged systems noh? unless i'm missing the point here, which i usually do HTH--------------------keeping it simple... |
 |
|
|
anilinsqlteam
Starting Member
9 Posts |
Posted - 2006-10-13 : 00:23:08
|
| Thanks for the reply.In resond to your answer I want to know is that, when a deadlock is detect by sql, sql allow one transaction and discard the other transaction.(asume only two transaction are the cause for deadlock)So the transaction allowed will be success and the transaction discarded will be roolback.This should not affect the database connection. Please clarify little more.RegardsAnil |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-10-13 : 01:21:22
|
| correct, it's called the deadlock victimit shouldn't affect db connections unless it's an error in which case if unhandled will exit the apps and break the connection--------------------keeping it simple... |
 |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-10-13 : 04:46:26
|
| I think it does kill the connection, but I could be wrong.-------Moo. :) |
 |
|
|
|
|
|