SQL Server and the Plan Guides, An easy way create and utilize!

Hi Guys!

First of all I must say a big thank you for the first five thousands visualizations of this my Blog. I am really very proud of it! Thank you so much!
 
Today i will show you how to create a Plan Guide in order to resolve, for example, parameter sniffing issues.

I hope you enjoy this post!

Introduction

It was November when we spoke about parameter sniffing (read here. )
We have seen that parameter sniffing is not necessary a bad thing.
Parametrization sniffing, instead, could be a problem if your data is distribuited unevenly!

Today for this first post of february I will show you a way to solve this problem through the creation of a Plan Guide
However, before talking of Plan Guide, we do also a small summary about unevenly distributed data.

Let's start!

Recap about not evenly distribuited data

Suppose we have two tables where we store our orders.
OrdTes represents the header of the documents while OrdRig its rows.
A document can have one or more lines.

Suppose that the data is not distributed evenly.

What does it mean?

It means that if i execute the query below with the parameter @P1 equal to 100 the Query returns 300.000 Row


 exec sp_executesql N'select ft.id,SUM(fr.Qta1) from OrdRig fr Join OrdTes ft on fr.IDORDTES = ft.id where fr.QTA1 = @P1 group by ft.id
',N'@P1 int', 100
 
While, if i execute the same query with the parameter @1 equal to 10 it returns just 1000 rows. 

 exec sp_executesql N' select ft.id,SUM(fr.Qta1) from OrdRig fr Join OrdTes ft on fr.IDORDTES = ft.id where fr.QTA1 = @P1 group by ft.id
',N'@P1 int', 10

With unevenly distribuited data we could have sniffing problems.

But why? 
 
Because the execution plan of the first query executed will be stored in the plan cache and this execution plan will be reused for all the subsequent queries. 
 
However note that two Queries have different execution plans.
 
 
 
 
So how to resolve this problem if you can’t change your Query? 
 
Suppose infact that your Query is inside an application that you can’t modify..
 
The solution in this case is to create a plan guide in order to force the Query optimizer to recompile your Query at each execution.
 

The Plan Guide

What is a Plan Guide?

A Plan Guide is essentially a way to modify the execution plan of a Query.
Through a plan guide we can apply to our query a series of hint.

Let's see how to create a Plan Guide.

First of all capture your Query execution through the SQL Server profiler.
 
Remember to specify these options:



Start the SQL Server Profiler and execute your Query from the management studio:


 Exec sp_executesql N'select ft.id,SUM(fr.Qta1) from OrdRig fr Join OrdTes ft on fr.IDORDTES = ft.id where fr.QTA1 = @P1 group by ft.id
',N'@P1 int', 100
 
Then take a look to the SQL Server profiler :



Now Copy exactly (spaces included) the text as returned by the profiler and paste it in the @stmt and @params parameters.
 
In this moment you can specify your options in the @hint parameter.
In this case (in blu) i have specified the recompile option.
       
EXEC sp_create_plan_guide
@name = N'RICALCOLO',
@stmt = N'select ft.id,SUM(fr.Qta1) from OrdRig fr Join OrdTes ft on fr.IDORDTES = ft.id where fr.QTA1 = @P1 group by ft.id
',
@type = N'SQL',
@module_or_batch = NULL,
@params = N'@P1 int',
@hints = N'OPTION (RECOMPILE)'
GO


Then execute it! 
 
Compliments...your first plan guide is now created!


But now, how to verify that your queries are using the plan guide? 

Again using the SQL Server Profiler.
Just runing your query again.

You must see, inside the profiler, a row with the name of your plan guide.



Yes our plan guide is effectivery used.

Now using the RECOMPILE OPTION your Queries will be always recompiled each time it will be executed.

As usually each solution has its own PROs and CONs.
 
The PRO is that every time you will execute the Query you will have the right execution plan.
The CONS is that generating the execution plan whenever is expensive and time consuming.

Another solution..
Through a plan guide we could force other behaviors for example using hints such as ForceSeek.

 

Finally,  for the sake of the completeness, you can view your plan guides in the menu Programmability / Plan Guide:


 

That's all for today!
 
I hope you enjoyed this Post  
If so remember to subscribe to the blog please!


Luca Biondi @ SQLServerPerformance blog!

 

 
 
 
 
 
 
 
 
 

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more