Disassembling the SQL Server parser. The LGetToken procedure - part 1

Happy Sunday my dear friends and welcome back to this blog!

Today we will talk about the parser component of SQL Server.

We keep disassemble the parser as we already done here:

I don't think it has ever been done before and I don't even know if I will end up ...maybe I could probably write a book about it, who knows! 

...but today I want to show you a few interesting things.


So start your management studio enter a simple select command, start a debugger like WINDBG
...and of course "happy reading"!


The LGetToken procedure

The LGetToken procedure is so defined:

void LGetToken(uint **param_1,uint *param_2,ushort **param_3)

The param_2 contain the pointer to the sql command.

This procedure is called by the yylex procedure in order to parse the T-SQL commands you send to the database engine of SQL Server.

Inside this procedure you will find and validate the statements inputed as token ("Select", "From", "Customer")

Our tokens are decoded while functions GetChar and Gen_Get_Lex (we talked about in the past posts) are used.


Taking a look to the source code, we can find this part where we are parsing the command string skipping all the not printable charaters.

Take a look to the Get_Gen_Lex




Now you know that you can add not printable character befor your statement: simply they will be skipped!

Now is searched for the charater N (0x4e) followed by the character ' (0x27).

The N' prefix indicate the unicode prefix.

For now we don't care if we found a "$" (0x24) 

Another step ahead!

Remember that we are parsing the command "SELECT * FROM Customer"
...And we are exactly reading the 'S' char.

We have a SWITCH statement.

The Get_Gen_Lex will return the value "1" since means all the alphatetical characters from 'a' to 'z' plus characters: "_" , "@" ,  "#"

 




Let's see now what's happen..

We are parsing the input stream char by char (rememeber that the current charater is in params[164]).

We will continue reading char by char until we read an line feed (0xlf) character.


Ok  we have almost identified a token.

TO BE CONTINUED!




 

Thanks to all! I wish you a great great week! 

Please subscribe to this blog if you found it helpful!

But again more important remember to think big and always share the knowledge!












Previous post: SQL Server, speaking about ALIAS ...learn the rule

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?  ...
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 ...
Read more