Skip to content

Commit 24913c6

Browse files
authored
Merge pull request #9596 from dschall/patch-1
Update sys-query-store-plan-transact-sql.md
2 parents b79fc2c + bd67c7f commit 24913c6

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/relational-databases/system-catalog-views/sys-query-store-plan-transact-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=azure-sqldw-latest||>=sq
4141
|**is_forced_plan**|**bit**|Plan is marked as forced when user executes stored procedure `sys.sp_query_store_force_plan`. Forcing mechanism *does not guarantee* that exactly this plan will be used for the query referenced by `query_id`. Plan forcing causes query to be compiled again and typically produces exactly the same or similar plan to the plan referenced by `plan_id`. If plan forcing does not succeed, `force_failure_count` is incremented and `last_force_failure_reason` is populated with the failure reason. <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns zero (0).|
4242
|**is_natively_compiled**|**bit**|Plan includes natively compiled memory optimized procedures. (0 = FALSE, 1 = TRUE). <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns zero (0).|
4343
|**force_failure_count**|**bigint**|Number of times that forcing this plan has failed. It can be incremented only when the query is recompiled (*not on every execution*). It is reset to 0 every time `is_plan_forced` is changed from **FALSE** to **TRUE**. <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns zero (0).|
44-
|**last_force_failure_reason**|**int**|Reason why plan forcing failed.<br /><br /> 0: no failure, otherwise error number of the error that caused the forcing to fail<br /><br /> 8637: ONLINE_INDEX_BUILD<br /><br />8675: OPTIMIZATION_REPLAY_FAILED<BR/><BR/>8683: INVALID_STARJOIN<br /><br /> 8684: TIME_OUT<br /><br /> 8689: NO_DB<br /><br /> 8690: HINT_CONFLICT<br /><br /> 8691: SETOPT_CONFLICT<br /><br /> 8694: DQ_NO_FORCING_SUPPORTED<br /><br /> 8698: NO_PLAN<br /><br /> 8712: NO_INDEX<br /><br /> 8713: VIEW_COMPILE_FAILED<br /><br />\<other value>: GENERAL_FAILURE <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns zero (0).|
45-
|**last_force_failure_reason_desc**|**nvarchar(128)**|Textual description of `last_force_failure_reason`.<br /><br /> ONLINE_INDEX_BUILD: query tries to modify data while target table has an index that is being built online<br /><br />OPTIMIZATION_REPLAY_FAILED: The optimization replay script failed to execute.<BR/><BR/>INVALID_STARJOIN: plan contains invalid StarJoin specification<br /><br /> TIME_OUT: Optimizer exceeded number of allowed operations while searching for plan specified by forced plan<br /><br /> NO_DB: A database specified in the plan does not exist<br /><br /> HINT_CONFLICT: Query cannot be compiled because plan conflicts with a query hint<br /><br /> DQ_NO_FORCING_SUPPORTED: Cannot execute query because plan conflicts with use of distributed query or full-text operations.<br /><br /> NO_PLAN: Query processor could not produce query plan because forced plan could not be verified to be valid for the query<br /><br /> NO_INDEX: Index specified in plan no longer exists<br /><br /> VIEW_COMPILE_FAILED: Could not force query plan because of a problem in an indexed view referenced in the plan<br /><br />GENERAL_FAILURE: general forcing error (not covered with other reasons) <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns `NONE`.|
44+
|**last_force_failure_reason**|**int**|Reason why plan forcing failed.<br /><br /> 0: no failure, otherwise error number of the error that caused the forcing to fail<br /><br /> 3617: COMPILATION_ABORTED_BY_CLIENT<br /><br /> 8637: ONLINE_INDEX_BUILD<br /><br />8675: OPTIMIZATION_REPLAY_FAILED<BR/><BR/>8683: INVALID_STARJOIN<br /><br /> 8684: TIME_OUT<br /><br /> 8689: NO_DB<br /><br /> 8690: HINT_CONFLICT<br /><br /> 8691: SETOPT_CONFLICT<br /><br /> 8694: DQ_NO_FORCING_SUPPORTED<br /><br /> 8698: NO_PLAN<br /><br /> 8712: NO_INDEX<br /><br /> 8713: VIEW_COMPILE_FAILED<br /><br />\<other value>: GENERAL_FAILURE <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns zero (0).|
45+
|**last_force_failure_reason_desc**|**nvarchar(128)**|Textual description of `last_force_failure_reason`.<br /><br /> COMPILATION_ABORTED_BY_CLIENT: query compilation was aborted by client before it completed<br /><br /> ONLINE_INDEX_BUILD: query tries to modify data while target table has an index that is being built online<br /><br />OPTIMIZATION_REPLAY_FAILED: The optimization replay script failed to execute.<BR/><BR/>INVALID_STARJOIN: plan contains invalid StarJoin specification<br /><br /> TIME_OUT: Optimizer exceeded number of allowed operations while searching for plan specified by forced plan<br /><br /> NO_DB: A database specified in the plan does not exist<br /><br /> HINT_CONFLICT: Query cannot be compiled because plan conflicts with a query hint<br /><br /> DQ_NO_FORCING_SUPPORTED: Cannot execute query because plan conflicts with use of distributed query or full-text operations.<br /><br /> NO_PLAN: Query processor could not produce query plan because forced plan could not be verified to be valid for the query<br /><br /> NO_INDEX: Index specified in plan no longer exists<br /><br /> VIEW_COMPILE_FAILED: Could not force query plan because of a problem in an indexed view referenced in the plan<br /><br />GENERAL_FAILURE: general forcing error (not covered with other reasons) <br/>**Note:** [!INCLUDE [ssazuresynapse_md](../../includes/ssazuresynapse-md.md)] always returns `NONE`.|
4646
|**count_compiles**|**bigint**|Plan compilation statistics.|
4747
|**initial_compile_start_time**|**datetimeoffset**|Plan compilation statistics.|
4848
|**last_compile_start_time**|**datetimeoffset**|Plan compilation statistics.|

0 commit comments

Comments
 (0)