A special post: One day at work with me!

Hi Guys,

I just got back from the cinema where I watched The Lost City with Sandra Bullock and Channing Tatum. 

Yess, a cool film! But now it is the time to turn on the laptop and, as promised in the last post, click on the publish button for a special post!

 

A day at work with me!

Remember, when a day starts before 8:00 with a business phone call it's usually never a good sign!

And if an important customer is blocked and you start the day without coffee, this is all ... confirmed!

Ok, let's be more precise! When the call from your customer "X" arrives, whose procedure for calculating the stocks of his material is no longer successful!

Enjoy the reading!


Deadlock & warehouse stock

It's urgent! Let's connect with the customer to see what's happening!

What to say ...often an error message can tell us a lot:


Well, yes (houston!) we have a deadlock problem!
 

And now, how to proceed? We activate a couple of trace flags:


DBCC TRACEON (1204,-1)

GO

DBCC TRACEON (1222,-1)

These trace flags allow us to log deadlocks to the SQL Server error log as well

Very good! 

Let us now launch the procedure that goes into deadlock again and let's see what the SQL Server error log contains.

You can find the log here:

 

Now click on the Current item and look at the Log:

 

We can see a lot of information, but the most important is the collision of the two queries.

For privacy reasons, I have hidden the text of the Queries but inside the two green box at the bottom we can see the blocked Query and the Blocking query.

In the green box at the top you can see on which table the two queries collide.

Now some time has passed! ... and I know that sometimes the customer would have already called to find out how to proceed with the resolution ... it takes a cool head but we already have the most important information!

What can we do now?

 

Profiler

We have to run the procedure again!
This time, however, we will put it under profiler!

How should you set up the profiler?
I usually always select check to track stored procedures and triggers.


This time I need to know also when a rollback occurs:


I need to see if recompilation occur:



And I need to see also the execution plan:




Now run the procedure again and take a look to the profiler.

The same Query executed 4 times, reads twice a number of pages and twice a different and much greater number of pages.


Furthermore, not seeing any recompilation from the profiler, we come to understand that we have a sniffing problem!

 

We have a so called sniffing problem!

We have talked about sniffing many times on this blog, if you want to know more you can search here.

Just two words to say where this problem arose:

When SQL Server solve a Query generate an execution plan and this this operation is quite heavy SQL Server store the execution plan in the cache plan.

As said this happens for performance reason.

In fact if I run the same query SQL Server will reuse the same execution plan and the execution time will be less.

However if my query has parameters a problem arose: the execution plan has been generated with some parameters while I execute the query with other parameters.

The execution plan may be not optimal.

This happens furthermore when the Query extract data distributed unevenly. For example, when I ask for the number of orders a customer has placed, I might have a customer who has placed many orders while others have not placed any.


Solve a sniffing problem 

Today we need to solve this problem.

What could we do? We could create an adhoc index.

I created a custom index.This index will allow to the Query to read less rows and thus have less probability to read rows readed or updated by other Queries.
Some tests usually need to be done.

In the end I created a covering index and I verified that it is used by my SELECT and not by the UPDATE

.... et voilà the deadlock is disappeared and the procedure is working again!

This time it was simple but we made it friends! We made it!
And now a good coffee!



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