It's not a secret that a deadlock - it's not very good. Definition of deadlock is straightforward and quite clear: This is an exceptional situation when two concurrent queries request the same resources but in a different order. Classic deadlock can occur when two concurrent transactions are modifying data from the two tables in a different order. Unfortunately, in real world deadlocks often are more complex and unobvious. One of the rules, which I always keep in mind, sounds: "You can not design a database, in which the occurrence of deadlock is impossible". And we should deal with them. The algorithm is quite simple: catch, analyze, fix. In practice, the process can be challenging and can require different types of analysis. 

In this session, we will learn and remind some basics about Locks and Transaction Isolation Levels and then analyze and solve as many deadlocks as we can during the session timeframe.
(no tags)
The video is not available to view online.