Causes stored procedures, triggers, and user-defined functions to be recompiled the next time that they are run. It does this by dropping the existing plan from the procedure cache forcing a new plan to be created the next time that the procedure or trigger is run. In a SQL Server Profiler collection, the event
SP:CacheInsert is logged instead of the event
sp_recompile [ @objname = ] 'object'
[ @objname= ] 'object'
The qualified or unqualified name of a stored procedure, trigger, table, view, or user-defined function in the current database. object is nvarchar(776), with no default. If object is the name of a stored procedure, trigger, or user-defined function, the stored procedure, trigger, or function will be recompiled the next time that it is run. If object is the name of a table or view, all the stored procedures, triggers, or user-defined functions that reference the table or view will be recompiled the next time that they are run.
Return Code Values
0 (success) or a nonzero number (failure)
sp_recompile looks for an object in the current database only.
The queries used by stored procedures, or triggers, and user-defined functions are optimized only when they are compiled. As indexes or other changes that affect statistics are made to the database, compiled stored procedures, triggers, and user-defined functions may lose efficiency. By recompiling stored procedures and triggers that act on a table, you can reoptimize the queries.
Proactive execution of this stored procedure is usually unnecessary. SQL Server automatically recompiles stored procedures, triggers, and user-defined functions when it is advantageous. There are a variety of reasons the database engine may choose to recompile objects. Most commonly, automatic recompilation follows changes to the underlying cardinality estimate because of automatic or manual statistics updates.
Recompiling a stored procedure with every execution is one of the less efficient ways to combat query plan issues caused by parameterization. The feature Parameter Sensitive Plan optimization introduced in SQL Server 2022 (16.x) attempts to mitigate this problem automatically. In prior versions, instead of calling
sp_recompile with each execution, consider:
- Append the WITH RECOMPILE option to the query, requiring a code change.
- Apply the
WITH RECOMPILEoption with a plan guide.
- Apply the
WITH RECOMPILEoption with a Query Store hint without making code changes.
- For more issues and discussion on this topic, see Resolving queries with parameter sensitive plan problems.
Requires ALTER permission on the specified object.
The following example causes stored procedures, triggers, and user-defined functions that act on the
Sales.Customer table to be recompiled the next time that they are run.
USE AdventureWorks2012; GO EXEC sp_recompile N'Sales.Customer'; GO
- CREATE PROCEDURE (Transact-SQL)
- CREATE TRIGGER (Transact-SQL)
- System Stored Procedures (Transact-SQL)
- SQL:StmtRecompile Event Class