Merge pull request #20276 from MicrosoftDocs/master

9/22 PM Publish

Author: huypub

docs/database-engine/availability-groups/windows/always-on-availability-groups-interoperability-sql-server.md

@@ -2,7 +2,7 @@
 title: "Always On availability groups: interoperability"
 description: "Describes the different features that can and cannot function alongside an Always On availability group."
 ms.custom: "seodec18"
-ms.date: "04/20/2017"
+ms.date: "09/15/2021"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: availability-groups
@@ -44,7 +44,8 @@ The following table lists [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-m
 
 The following features interoperate with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] with specific restrictions. See the linked topics for details.
 
-- Cross-database transactions/distributed transactions ([!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] and Windows Server 2016). For more information, see [Cross-Database Transactions and Distributed Transactions for Always On Availability Groups and Database Mirroring (SQL Server)](../../../database-engine/availability-groups/windows/transactions-always-on-availability-and-database-mirroring.md)
+- Cross-database transactions within the same SQL Server instance require [!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] SP2 and Windows Server 2016 or later, with some patching requirements. For more information, see [Cross-Database Transactions and Distributed Transactions for Always On Availability Groups and Database Mirroring (SQL Server)](../../../database-engine/availability-groups/windows/transactions-always-on-availability-and-database-mirroring.md)
+- Distributed transactions require [!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] SP2 and Windows Server 2012 R2 or later, with some patching requirements. For more information, see [Cross-Database Transactions and Distributed Transactions for Always On Availability Groups and Database Mirroring (SQL Server)](../../../database-engine/availability-groups/windows/transactions-always-on-availability-and-database-mirroring.md)
 - [Query statistics system data collector](../../../relational-databases/data-collection/system-data-collection-set-reports.md#Query) cannot reliably run in an environment with non-readable secondaries. To use query statistics system data collector, set all secondary availability group replicas to allow [read-access](configure-read-only-access-on-an-availability-replica-sql-server.md). 
 
 ## <a name="NoInterop"></a> Features that Do Not Interoperate with Always On Availability Groups
@@ -71,4 +72,4 @@ The following features interoperate with [!INCLUDE[ssHADR](../../../includes/ssh
 ## See Also
 
 [Overview of Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
-[Prerequisites, Restrictions, and Recommendations for Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md)
+[Prerequisites, Restrictions, and Recommendations for Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md)

docs/machine-learning/install/sql-ml-cab-downloads.md

@@ -3,7 +3,7 @@ title: CAB download updates for offline install
 description: Download Python and R CAB files for SQL Server Machine Learning Services. These CAB files contain updates to the Machine Learning Services (Python and R) feature and are used when installing SQL Server on a server without internet access.
 ms.prod: sql
 ms.technology: machine-learning-services
-ms.date: 03/25/2021
+ms.date: 09/22/2021
 ms.topic: how-to
 author: garyericson
 ms.author: garye
@@ -31,7 +31,7 @@ Start with a baseline installation. On SQL Server Machine Learning Services, the
 ::: moniker-end
 
 ::: moniker range="=sql-server-2016"
-Start with a baseline installation.  On SQL Server 2016 R Services, you can start with the initial release, SP1, or SP2. 
+Start with a baseline installation.  On SQL Server 2016 R Services, you can start with the initial release, SP1, SP2, or SP3. 
 ::: moniker-end
 
 You can also apply cumulative updates.
@@ -158,7 +158,7 @@ For SQL Server 2016 R Services, baseline releases are either the RTM version or
 
 |Release  |Download link  |
 |---------|---------------|
-|**SQL Server 2016 SP2 CU14-CU15**     |
+|**SQL Server 2016 SP2 CU14-CU15** <br>&<br> **SQL Server 2016 SP3**     |
 |Microsoft R Open      |[SRO_3.5.2.777_1033.cab](https://go.microsoft.com/fwlink/?linkid=2134897)|
 |Microsoft R Server    |[SRS_9.4.7.958_1033.cab](https://go.microsoft.com/fwlink/?linkid=2136942)|
 |**SQL Server 2016 SP2 CU6-CU13**     |

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -62,8 +62,8 @@ The following table lists and describes the trace flags that are available in [!
 |<a name="tf102"></a>**102**|Increases the verboseness of the merge replication agent logging and directs it to the *\<Distribution server>..msmerge_history* table.<br /><br />**IMPORTANT:** Trace flag 102 can only be enabled for the [Replication Merge Agent](../../relational-databases/replication/agents/replication-merge-agent.md) using the **-T** option when executing **replmerg.exe** from the command prompt.<br /><br />**WARNING:** Trace flag 102 is not meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. For more information, see this [Microsoft Support article](https://mskb.pkisolutions.com/kb/2892633).<br /><br />**Scope**: Replication Merge Agent only|
 |<a name="tf139"></a>**139**| Forces correct conversion semantics in the scope of DBCC check commands like [DBCC CHECKDB](../../t-sql/database-console-commands/dbcc-checkdb-transact-sql.md), [DBCC CHECKTABLE](../../t-sql/database-console-commands/dbcc-checktable-transact-sql.md) and [DBCC CHECKCONSTRAINTS](../../t-sql/database-console-commands/dbcc-checkconstraints-transact-sql.md), when analyzing the improved precision and conversion logic introduced with compatibility level 130 for specific data types, on a database that has a lower compatibility level. For more information, see this [Microsoft Support article](https://support.microsoft.com/help/4010261).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] RTM CU3, [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP1 and higher builds.<br /><br />**WARNING:** Trace flag 139 is not meant to be enabled continuously in a production environment, and should be used for the sole purpose of performing database validation checks described in this [Microsoft Support article](https://support.microsoft.com/help/4010261). It should be immediately disabled after validation checks are completed.<br /><br />**Scope**: global only|
 |<a name="tf174"></a>**174**|Increases the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] plan cache bucket count from 40,009 to 160,001 on 64-bit systems. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3026083).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global only|
-|<a name="tf176">**176**|Enables a fix to address errors when rebuilding partitions online for tables that contain a computed partitioning column. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3213683) and this [Microsoft Support article](https://support.microsoft.com/kb/4541096).<br /><br />**Scope**: global or session|
-|<a name="tf205">**205**|Reports to the error log when a statistics-dependent stored procedure is being recompiled as a result of auto-update statistics. For more information, see this [Microsoft Support article](https://mskb.pkisolutions.com/kb/195565).<br /><br />**Note:** This trace flag requires trace flag [3605](#3605) to be enabled.<br /><br />**Scope**: global only|
+|<a name="tf176"></a>**176**|Enables a fix to address errors when rebuilding partitions online for tables that contain a computed partitioning column. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3213683) and this [Microsoft Support article](https://support.microsoft.com/kb/4541096).<br /><br />**Scope**: global or session|
+|<a name="tf205"></a>**205**|Reports to the error log when a statistics-dependent stored procedure is being recompiled as a result of auto-update statistics. For more information, see this [Microsoft Support article](https://mskb.pkisolutions.com/kb/195565).<br /><br />**Note:** This trace flag requires trace flag [3605](#3605) to be enabled.<br /><br />**Scope**: global only|
 |<a name="tf260"></a>**260**|Prints versioning information about extended stored procedure dynamic-link libraries (DLLs). For more information about **GetXpVersion()**, see [Creating Extended Stored Procedures](../../relational-databases/extended-stored-procedures-programming/creating-extended-stored-procedures.md).<br /><br />**Scope:** global or session|
 |<a name="tf272"></a>**272**|Disables identity pre-allocation to avoid gaps in the values of an identity column in cases where the server restarts unexpectedly or fails over to a secondary server. Note that identity caching is used to improve INSERT performance on tables with identity columns.<br /><br />**Note:** Starting with [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)], to accomplish this at the database level, see the IDENTITY_CACHE option in [ALTER DATABASE SCOPED CONFIGURATION &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Scope**: global only|
 |<a name="tf460"></a>**460**|Replaces data truncation message ID [8152](../../relational-databases/errors-events/database-engine-events-and-errors.md#errors-8000-to-8999) with message ID [2628](../../relational-databases/errors-events/database-engine-events-and-errors.md#errors-2000-to-2999). For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4468101).<br /><br />Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], to accomplish this at the database level, see the VERBOSE_TRUNCATION_WARNINGS option in [ALTER DATABASE SCOPED CONFIGURATION &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU12 and higher builds.<br /><br />**Note:** Starting with database compatibility level 150, message ID 2628 is the default and this trace flag has no effect.<br /><br />**Scope**: global or session|