Re: Disabling automatic kill of a deadlocked process

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: RyGuyVan (RyGuyVan_at_discussions.microsoft.com)
Date: 09/28/04


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.
>
>
>



Relevant Pages

  • Re: Disabling automatic kill of a deadlocked process
    ... > The reason I am asking is that for some reason the automatic kill is never ... Are you 100% certain is really was a *deadlock* and not just ordinary blocking? ... > occuring on the customer site and their dba doesn't know how this was ...
    (microsoft.public.sqlserver.server)
  • Re: Firefox browser - more info
    ... There is no possible reason for you to do this. ... Aside from disabling ... the usb ports, there is no way you can stop this behavior. ... using Firefox will void your warranty and cause your cat to ...
    (microsoft.public.windowsxp.general)
  • Re: Nikon super coolscan ( for Don or anybody )
    ... Like when I use the 120 film strip tray. ... Since ASF don't sell DEE separately, there was no reason to disable ... products for marketing reasons (like the aforementioned disabling of ...
    (comp.periphs.scanners)
  • Re: [PATCH 1/3] Separate IRQ-stacks from 4K-stacks option
    ... >> because it gives people a reason to do sloppy coding. ... > disabling nesting completely sounds a bit too aggressive, ... disabling is actually not a bad idea; hard irq handlers run for a very short ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [patch 02/2] allow gcc4 to optimize unit-at-a-time
    ... >> a) support it ... > There was a reason for disabling it unconditionally in first place. ... > gcc before 4.00 then we should visit the reasons why it originally was ...
    (Linux-Kernel)