Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Avoiding deadlock
Message
From
12/10/2014 12:34:25
 
 
To
All
General information
Forum:
Microsoft SQL Server
Category:
Other
Title:
Avoiding deadlock
Environment versions
SQL Server:
SQL Server 2012
Application:
Web
Miscellaneous
Thread ID:
01609189
Message ID:
01609189
Views:
62
I have an issue about a deadlock, which happens very rarely, and I would like to know what could be the cause here.

The message is this:

"Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

This is the command:
DECLARE @LastAccess DateTime
DECLARE @Numero Int

SET @LastAccess='2014-10-10 21:07:45'
SET @Numero=24349

UPDATE Member SET LastAccess=@LastAccess WHERE Numero=@Numero
This update on the Member table can only be done by one person. So, there cannot be two updates done on that record at the same time. Why do I end up with a deadlock on some isolated situations?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Next
Reply
Map
View

Click here to load this message in the networking platform