![]() ![]() Actually, we can acquire a lock on different kind of resources (row identifier, key, page, table…) and using different modes (shared, exclusive…). In relational database management systems, locking is a mechanism that happens every time. We could intuitively understand it as a lock that leads to a dead end… So, what is a “deadlock”? Etymologically, it can be divided into two root words: “dead” and “lock”. Then we will see that SQL Server actually has some tools to help detect their occurrences and get everything we need to find and fix it, although the solution might be simpler said than done… So, in the following sections, we will try to understand, basically, what a deadlock is and how it occurs with a practical example in T-SQL. These actions would lead to either a lower occurrence frequency or a total disappearance of deadlock conditions. After reading this article you will be able to explain how a deadlock can occur and how we can get extended information about this deadlock so that we will be able to diagnose and take the appropriate actions. This article is the first one of a series that will focus on deadlock issues and reporting. Due to their nature and like any similar blocking situation, deadlocks can have a direct impact on user experience and the more they occur, the bigger the impact. Sometimes, poorly written code or lack of indexes will generate blocking conditions that we refer to as a“Deadlock”. As a DBA, I’ve been, more than, confronted with performance problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |