| title | Validate Plan Guides After Upgrade | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 06/13/2017 | |
| ms.prod | sql-server-2014 | |
| ms.reviewer | ||
| ms.technology | performance | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | a55ebd88-6f58-454d-b1c4-991b88add522 | |
| author | MikeRayMSFT | |
| ms.author | mikeray | |
| manager | craigg |
We recommend re-evaluating and testing plan guide definitions when you upgrade your application to a new release of [!INCLUDEssNoVersion]. Performance tuning requirements and plan guide matching behavior may change. Although an invalid plan guide will not cause a query to fail, the plan is compiled without using the plan guide and may not be the best choice. After upgrading a database to [!INCLUDEssCurrent], we recommend that you perform the following tasks:
-
Validate existing plan guides by using the sys.fn_validate_plan_guide function.
-
Use extended events to monitor for misguided plans for some period of time by using the Plan Guide Unsuccessful event.