Merge pull request #29527 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: rwestMSFT

docs/connect/ado-net/sqlclient-driver-support-lifecycle.md

@@ -27,9 +27,9 @@ New stable (GA) releases are published every six months on a regular cadence beg
 
 | Version | Official Release Date | Latest Patch Version | Patch Release Date | Support Level | End of Support |
 |--|--|--|--|--|--|
-| 5.1 | January 19, 2023 | 5.1.2 | October 26, 2023 | LTS | January 20, 2026 |
-| 4.0 | November 18, 2021 | 4.0.4 | October 30, 2023 | LTS | November 19, 2024 |
-| 3.1 | March 30, 2022 | 3.1.4 | October 31, 2023 | LTS | March 30, 2025 |
+| 5.1 | January 19, 2023 | 5.1.4 | January 9, 2024 | LTS | January 20, 2026 |
+| 4.0 | November 18, 2021 | 4.0.5 | January 9, 2024 | LTS | November 19, 2024 |
+| 3.1 | March 30, 2022 | 3.1.5 | January 9, 2024 | LTS | March 30, 2025 |
 
 ### Out of support releases
 
@@ -38,7 +38,7 @@ New stable (GA) releases are published every six months on a regular cadence beg
 | 5.0 | July 29, 2022 | 5.0.2 | March 31, 2023 | Current | July 19, 2023 |
 | 4.1 | January 31, 2022 | 4.1.1 | September 13, 2022 | Current | January 29, 2023 |
 | 3.0 | June 9, 2021 | 3.0.1 | September 24, 2021 | Current | May 18, 2022 |
-| 2.1 | November 19, 2020 | 2.1.6 | April 27, 2023 | LTS | November 20, 2023 |
+| 2.1 | November 19, 2020 | 2.1.7 | January 9, 2024 | LTS | November 20, 2023 |
 | 2.0 | June 16, 2020 | 2.0.1 | August 25, 2020 | Current | May 19, 2021 |
 | 1.1 | November 20, 2019 | 1.1.4 | March 10, 2021 | LTS | November 21, 2022 |
 | 1.0 | August 28, 2019 | 1.0.19269.1 | September 26, 2019 | Current | May 20, 2020 |

docs/linux/sql-server-linux-docker-container-configure.md

@@ -38,7 +38,7 @@ Your SQL Server configuration changes and database files are persisted in the co
 
 ### Mount a host directory as data volume
 
-The first option is to mount a directory on your host as a data volume in your container. To do that, use the `docker run` command with the `-v <host directory>:/var/opt/mssql` flag. This allows the data to be restored between container executions.
+The first option is to mount a directory on your host as a data volume in your container. To do that, use the `docker run` command with the `-v <host directory>:/var/opt/mssql` flag, where `<host directory>` is any given path. For instance: `C:\SQL` on Windows, or `~/sqlvolumes` on Linux. This allows the data to be restored between container executions.
 
 > [!NOTE]  
 > Containers for [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] and later versions automatically start up as non-root, while [!INCLUDE [sssql17-md](../includes/sssql17-md.md)] containers start as root by default. For more information on running SQL Server containers as non-root, see [Configure security](sql-server-linux-docker-container-security.md).

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

@@ -41,8 +41,8 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=azure-sqldw-latest||>=sq
 |**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).|
 |**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).|
 |**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).|
-|**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).|
-|**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`.|
+|**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).|
+|**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`.|
 |**count_compiles**|**bigint**|Plan compilation statistics.|
 |**initial_compile_start_time**|**datetimeoffset**|Plan compilation statistics.|
 |**last_compile_start_time**|**datetimeoffset**|Plan compilation statistics.|