SQL Server, Difference between a seek and a scan operation and the Latch coupling

Hi Guys,

During my last post i blogged about buffer latch (*) and the Last page insert latch contention problem.

(*) What is a Latch? ...As written in my previous post, which I recommend to read: Latches are synchronization primitives that are used by SQL Server to manage data concurrency and guarantee consistency of its in-memory structures like index, data pages and internal structures, such as non-leaf pages in a B-Tree.

Since it is very important to understand how latches work, today i will try to deepen. I will try to be as clear as possible even if the topic is not the simplest.

We will also understand what is the difference is between a seek and a scan operation.


Seek operation and Latch Coupling

Surely you already know that you can access data in SQL Server via an index with a seek or scan operation.
 
Doing a seek operation means that you will use the B-Tree structure to reach the leaf-level data pages.
 
First the Index Root Page is read, then an Index Page in the underlying level and finally the Data Page in the Leaf Level.
 
Buffer latches are placed on the pages in the three levels of the B-Tree
 

SQL Server B-Tree structure


Yes but in which order and how latches are placed on the data pages?
Let's do an example to be clearer!

An example

For our example we take a table with a clustered index on an integer field ID.
 
Using the DBCC IND (0,'nometabella',1) command wee see  the data pages from which our clustered index is composed:


As the theory says we have:
  • A page (id=61374) which is the index page at the Root level (level 2)
  • A page (id=61375) which is the data page at the intermediate level (level 1)
  • A page (id=2153365) which is the data page (level 0)
We now use extended events to trace when a latch is placed on a data table (latch_acquired) or when a latch is removed from a data page (latch_released).
 
Now doing a simple

SELECT ID FROM Tabella where ID = 1000
The clustered index is used. 
 
Look to the table below to see in what order and how latches are placed and removed:


You can see that the seek operation reads the root index page first.
To read this page:
  • A shared (SH) latch is placed on root index page 61374
Now the seek operation will read the intermediate index page.
To read this page:
  • A shared (SH) latch is placed on intermediate level index page 61375
  • A shared (SH) latch is released on root index page 61374  
Important: Only after successfully acquiring a latch of the intermediate level index page, the latch on the root index pages is released.
 
Then the seek operation will read the data page 2153365.
To read this page:
  • A shared (SH) latch is placed on data page 2153365
  • A shared (SH) latch is released on root index page 61374 
Again, a latch on the intermediate level index page is released only when the latch on the data page has been successfully acquired.

This way to proceed is called Latch Coupling and it is necessary because sql server follow a pointer from a page to another.

Finally we can say that a SEEK operation is much faster that a SCAN operation because it uses the B-Tree structure. A Seek operation has a complexity of O*Log(n) while a SCAN operation has a linear complexity of O*n.


That's all for today!
Luca



Comments

Post a Comment

I Post più popolari

SQL Server, execution plan and the lazy spool (clearly explained)

Image
Hi Guys, Welcome back! In one of the last posts we talked about Table Spool . We had explained what Spool are for by telling the somewhat curious story of the halloween problem . Here we specifically talked about a type of spool called Eager Spool   You can look to the execution plan below where the eager Spool is used to avoid the halloween problem in classic query of the "salary increase".. i suggest Well, if the story of the eager spool intrigued you, today instead we will speak about another type of Spool, the Lazy Spool . The Lazy spool Let's take a small step back. So, what is a Spool operation?  As we have already understood a spool operation is simply a temporary storage of data . Data are read from a source table and stored inside a worktable in the Tempdb database . While an Eager Spool is used to prevent the Halloween problem, the Lazy Spool is instead used to store data that will later be needed again when running a query . So, when a Lazy spool is used?    I
Read more

SQL Server, datetime vs. datetime2

Image
Hi guys, This time, in this post we will speak about datetime and datetime2 datatypes. We will talk about the pros and cons. We will talk about all the differences between the two types of data. Write me in the comments which type of data do you prefer between the two. Enjoy the reading!     Datetime Vs. Datetime2 First of all, it must be said that the datatype datetime is certainly the best known native format for storing a date in SQL Server. However, Microsoft has also been introducing a new type of data for many years now, also used to manage dates. It is in fact from SQL server 2008 that it is present in datetime2 data type. This "new" type of data was born primarily to have higher accuracy . Let's in fact talk about ... precision ! Datetime Certainly the datetime data type is not very precise and certainly there are many cases in which its precision is simply not sufficient. Let's see it with an example. Open the SQL Management studio (SSMS) and write the fo
Read more

La clausola NOLOCK. Approfondiamo e facciamo chiarezza!

Image
Ehi ragazzi! La domanda è di quelle importanti! Siete pronti per scoprire tutto ma proprio tutto sulla clausola NOLOCK?   Se la riposta è si, allora seguitemi! Oggi ne spiegheremo il funzionamento in maniera approfondita. Faremo una introduzione al concetto di tipi di LOCK Ed infine vedremo come mai una SELECT ne può bloccare un'altra. Non vi nascondo che il motivo di questo articolo è fare chiarezza. Su questo argomento si sentono spesso affermazioni “curiose” ma tra le tante questa è la prima: “ uso la SELECT con l’opzione WITH(LOCK) così non blocco le altre tabelle ”.   Ma, è proprio vero quanto affermato? Beh oggi facciamo il punto!   Buona lettura!     La clausola NOLOCK Diciamo subito per iniziare che cos’è la NOLOCK. NOLOCK è il nome di una clausola che è possibile specificare all’interno di uno statement di tipo SELECT utilizzando la seguente sintassi: SELECT * FROM TABELLA WITH (NOLOCK) Si noti che non possiamo utilizzare questa cl
Read more