Preventing deadlocks
From: Maury Markowitz (MauryMarkowitz_at_discussions.microsoft.com)
Date: 12/06/04
- Next message: Chris: "RE: SQL Timeout problem"
- Previous message: Adam Machanic: "Re: Correlated Subqueries?"
- Next in thread: Robert Davis: "RE: Preventing deadlocks"
- Reply: Robert Davis: "RE: Preventing deadlocks"
- Reply: David Gugick: "Re: Preventing deadlocks"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Dec 2004 12:07:06 -0800
I've noticed a couple of very nasty deadlocks on our new server lately, and
I'd like some advice on how to "ignore" them. What's happening is that
someone's machine and/or Access dies into the VB debugger in the middle of a
SELECT, and the process locks. This pretty much stops all access to the
server, and ends backups as well!
I don't see any way to prevent these problems on the user machine, so how to
I ignore them on the server? Is there some timeout I've forgot to set when we
set up the machine?
Also, when I attempt to kill the process in Manager it seems to either not
work, or take a very long time. Is this normal?
- Next message: Chris: "RE: SQL Timeout problem"
- Previous message: Adam Machanic: "Re: Correlated Subqueries?"
- Next in thread: Robert Davis: "RE: Preventing deadlocks"
- Reply: Robert Davis: "RE: Preventing deadlocks"
- Reply: David Gugick: "Re: Preventing deadlocks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|