Skip to main content

3 ways to recompile stored procedures

Requirement for Recompilation : 

When we create and execute a procedure it will compiled and create execution plan for the present state of the database . If we do changes into database structure, we should recompiling a procedure updates and optimizes the procedure’s query plan for those changes. This can improve the procedure’s processing performance.

Another reason to stress a procedure to recompile is to retro-act the "parameter sniffing". When SQL Server executes procedures, any parameter values that are used by the procedure when it compiles are connected as part of generating the query plan.

SQL Server also do automatic recompiling of procedure whenever Server is restarted.

3 ways to recompile manually :

1.) Directly writing in procedure.
2.) During execution of procedure.
3.) Ad-hoc manner from query prompt.

Directly writing in procedure.

Create PROCEDURE [dbo].[upTitle_Select]
@TitleID int = NULL,
@Title varchar(5) = NULL
WITH RECOMPILE
AS
BEGIN
SET NOCOUNT ON;
DECLARE @ErrorCode int;
SELECT @ErrorCode = @@ERROR;
.....
...
..
End

During execution of procedure
exec upTitle_Select 230, 'just Test' WITH RECOMPILE

Ad-hoc manner for query prompt.
sp_recompile 'upTitle_Select'

Comments

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription