Re: Disabling automatic kill of a deadlocked process
From: RyGuyVan (RyGuyVan_at_discussions.microsoft.com)
Date: 09/28/04
- Next message: Nigel Rivett: "RE: max number of columns in a query"
- Previous message: Steve Kass: "Re: ISNULL function does not work as expected on calculated field"
- In reply to: Adam Machanic: "Re: Disabling automatic kill of a deadlocked process"
- Next in thread: Tibor Karaszi: "Re: Disabling automatic kill of a deadlocked process"
- Reply: Tibor Karaszi: "Re: Disabling automatic kill of a deadlocked process"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Sep 2004 14:11:04 -0700
The reason I am asking is that for some reason the automatic kill is never
occuring on the customer site and their dba doesn't know how this was
disabled.
If I could figure how this is disabled, I could then hopefully get it
reenabled over there.
"Adam Machanic" wrote:
> No; leaving it untouched would mean leaving the condition in place and
> keeping locks on those objects until someone can come clean it up by
> manually killing them. Not a good idea, IMO. This could mean that entire
> tables will remain locked until you come fix it.
>
>
> "RyGuy Van" <RyGuy Van@discussions.microsoft.com> wrote in message
> news:0980BFE6-A1F5-43B5-A09C-5AE7364A0B3D@microsoft.com...
> > Is there a way in sql server of disabling the feature,where a process is
> > automatically chosen as a victim, when a deadlock occurs?
> >
> > I would like to have the deadlock left untouched so that it can be
> manually
> > investigated and resolved.
>
>
>
- Next message: Nigel Rivett: "RE: max number of columns in a query"
- Previous message: Steve Kass: "Re: ISNULL function does not work as expected on calculated field"
- In reply to: Adam Machanic: "Re: Disabling automatic kill of a deadlocked process"
- Next in thread: Tibor Karaszi: "Re: Disabling automatic kill of a deadlocked process"
- Reply: Tibor Karaszi: "Re: Disabling automatic kill of a deadlocked process"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|