Verifies the validity of the specified plan guide. The sys.fn_validate_plan_guide function returns the first error message that is encountered when the plan guide is applied to its query. An empty rowset is returned when the plan guide is valid. Plan guides can become invalid after changes are made to the physical design of the database. For example, if a plan guide specifies a particular index and that index is subsequently dropped, the query will no longer be able to use the plan guide.
By validating a plan guide, you can determine whether the guide can be used by the optimizer without modification. Based on the results of the function, you can decide to drop the plan guide and retune the query or modify the database design, for example, by re-creating the index specified in the plan guide.
OBJECT-scoped plan guides require VIEW DEFINITION or ALTER permission on the referenced object and permissions to compile the query or batch that is provided in the plan guide. For example, if a batch contains SELECT statements, SELECT permissions on the referenced objects are required.
SQL- or TEMPLATE-scoped plan guides require ALTER permission on the database and permissions to compile the query or batch that is provided in the plan guide. For example, if a batch contains SELECT statements, SELECT permissions on the referenced objects are required.
A. Validating all plan guides in a database
The following example checks the validity of all plan guides in the current database. If an empty result set is returned, all plan guides are valid.
USE AdventureWorks2012; GO SELECT plan_guide_id, msgnum, severity, state, message FROM sys.plan_guides CROSS APPLY fn_validate_plan_guide(plan_guide_id); GO
B. Testing plan guide validation before implementing a change to the database
The following example uses an explicit transaction to drop an index. The sys.fn_validate_plan_guide function is executed to determine whether this action will invalidate any plan guides in the database. Based on the results of the function, the DROP INDEX statement is either committed or the transaction is rolled back, and the index is not dropped.
USE AdventureWorks2012; GO BEGIN TRANSACTION; DROP INDEX IX_SalesOrderHeader_CustomerID ON Sales.SalesOrderHeader; -- Check for invalid plan guides. IF EXISTS (SELECT plan_guide_id, msgnum, severity, state, message FROM sys.plan_guides CROSS APPLY sys.fn_validate_plan_guide(plan_guide_id)) ROLLBACK TRANSACTION; ELSE COMMIT TRANSACTION; GO