Merge pull request #7157 from stevestein/sqlseattle-fix-9.9

Sqlseattle fix 9.9

Author: PRMerger9

docs/2014/relational-databases/replication/agents/replication-snapshot-agent.md

@@ -1,7 +1,7 @@
 ---
 title: "Replication Snapshot Agent | Microsoft Docs"
 ms.custom: ""
-ms.date: "06/13/2017"
+ms.date: "09/07/2018"
 ms.prod: "sql-server-2014"
 ms.reviewer: ""
 ms.suite: ""
@@ -56,7 +56,8 @@ manager: craigg
 [-MaxNetworkOptimization [0|1]]  
 [-Outputoutput_path_and_file_name]  
 [-OutputVerboseLevel [0|1|2] ]  
-[-PacketSizepacket_size]  
+[-PacketSizepacket_size]
+[-PrefetchTables [0|1] ]  
 [-ProfileNameprofile_name]  
 [-PublisherDBpublisher_database]  
 [-PublisherDeadlockPriority [-1|0|1] ]  
@@ -188,6 +189,14 @@ manager: craigg
 |**0**|Only error messages are printed.|  
 |**1** (default)|All the progress report messages are printed (default).|  
 |**2**|All error messages and progress report messages are printed, which is useful for debugging.|  
+
+ **-PrefetchTables** [ **0**| **1**]  
+ Optional parameter that specifies if the table objects will be prefetched and cached.  The default behavior is to prefetch certain table properties using SMO component based on an internal calculation.  This parameter can be helpful in scenarions where SMO prefetch operation takes considerable longer to run. If this parameter is not used, this decision is made at runtime based on the percentage of tables that are added as articles to the publication.  
+  
+|OutputVerboseLevel value|Description|  
+|------------------------------|-----------------|  
+|**0**|Call to Prefetch method of SMO component is disabled.|  
+|**1**|Snapshot Agent will call Prefetch method to cache some table properties using SMO|  
 
  **-PacketSize** *packet_size*  
  Is the packet size (in bytes) used by the Snapshot Agent when connecting to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. The default value is 8192 bytes.  

docs/advanced-analytics/install/sql-machine-learning-services-windows-install.md

@@ -1,9 +1,10 @@
 ---
 title: Install SQL Server Machine Learning Services (In-Database) on Windows | Microsoft Docs
+description: R in SQL Server or Python on SQL Server is available when you install SQL Server 2017 Machine Learning Services on Windows.
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 08/15/2018  
+ms.date: 09/08/2018  
 ms.topic: conceptual
 author: HeidiSteen
 ms.author: heidist
@@ -12,7 +13,7 @@ manager: cgronlun
 # Install SQL Server Machine Learning Services
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
 
-Starting in SQL Server 2017, R and Python support for in-database analytics is provided in SQL Server Machine Learning Services, the successor to R Services feature introduced in SQL Server 2016. Function libraries are available in R and Python and run as external script on a database engine instance. 
+Starting in SQL Server 2017, R and Python support for in-database analytics is provided in SQL Server Machine Learning Services, the successor to [SQL Server R Services](../r/sql-server-r-services.md) introduced in SQL Server 2016. Function libraries are available in R and Python and run as external script on a database engine instance. 
 
 This article explains how to install the machine learning component by running the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] setup wizard, and following the on-screen prompts.
 

docs/advanced-analytics/install/sql-r-services-windows-install.md

@@ -1,9 +1,10 @@
 ---
 title: Install SQL Server 2016 R Services (In-Database) | Microsoft Docs
+description: R in SQL Server is available when you install SQL Server 2016 R Services on Windows.
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 04/15/2018
+ms.date: 09/08/2018
 ms.topic: conceptual
 author: HeidiSteen
 ms.author: heidist
@@ -12,11 +13,11 @@ manager: cgronlun
 # Install SQL Server 2016 R Services
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
 
-This article explains how to install and configure **SQL Server 2016 R Services (In-Database)**. If you have SQL Server 2016, install this feature to enable execution of R code in SQL Server.
+This article explains how to install and configure **SQL Server 2016 R Services**. If you have SQL Server 2016, install this feature to enable execution of R code in SQL Server.
 
-## <a name="bkmk_prereqs"> </a> Pre-install checklist
+In SQL Server 2017, R integration is offered in [Machine Learning Services](../r/r-server-standalone.md), reflecting the addition of Python. If you want R integration and have SQL Server 2017 installation media, see [Install SQL Server 2017 Machine Learning Services](sql-machine-learning-services-windows-install.md) to add the feature. 
 
-+ SQL Server 2016 setup is required if you want to install R Services. If instead you have SQL Server 2017 installation media, you should install [SQL Server 2017 Machine Learning Services (In-Database)](sql-machine-learning-services-windows-install.md) to get R integration for that version of SQL Server.
+## <a name="bkmk_prereqs"> </a> Pre-install checklist
 
 + A database engine instance is required. You cannot install just R, although you can add it incrementally to an existing instance.
 
@@ -26,7 +27,7 @@ This article explains how to install and configure **SQL Server 2016 R Services
 
 + Do not install **Shared Features** > **R Server (Standalone)** on the same computer running an in-database instance. 
 
-+ Side-by-side installation with other versions of R and Python are possible because the SQL Server instance uses its own copies of the open-source R and Anaconda distributions. However, running code that uses R and Python on the SQL Server computer outside SQL Server can lead to various problems:
+  Side-by-side installation with other versions of R and Python are possible because the SQL Server instance uses its own copies of the open-source R and Anaconda distributions. However, running code that uses R and Python on the SQL Server computer outside SQL Server can lead to various problems:
 
   + You use a different library and different executable, and get different results, than you do when you are running in SQL Server.
   + R and Python scripts running in external libraries cannot be managed by SQL Server, leading to resource contention.

docs/relational-databases/replication/agents/replication-snapshot-agent.md

@@ -1,7 +1,7 @@
 ---
 title: "Replication Snapshot Agent | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "replication"
@@ -59,6 +59,7 @@ snapshot [ -?]
 [-Output output_path_and_file_name]  
 [-OutputVerboseLevel [0|1|2] ]  
 [-PacketSize packet_size]  
+[-PrefetchTables [0|1] ]  
 [-ProfileName profile_name]  
 [-PublisherDB publisher_database]  
 [-PublisherDeadlockPriority [-1|0|1] ]  
@@ -196,7 +197,15 @@ snapshot [ -?]
 
 > [!NOTE]  
 >  Do not change the packet size unless you are certain that it will improve performance. For most applications, the default packet size is best.  
+
+**-PrefetchTables** [ **0**| **1**]  
+ Optional parameter that specifies if the table objects will be prefetched and cached.  The default behavior is to prefetch certain table properties using SMO component based on an internal calculation.  This parameter can be helpful in scenarions where SMO prefetch operation takes considerable longer to run. If this parameter is not used, this decision is made at runtime based on the percentage of tables that are added as articles to the publication.  
 
+|OutputVerboseLevel value|Description|  
+|------------------------------|-----------------|  
+|**0**|Call to Prefetch method of SMO component is disabled.|  
+|**1**|Snapshot Agent will call Prefetch method to cache some table properties using SMO|  
+
  **-ProfileName** *profile_name*  
  Specifies an agent profile to use for agent parameters. If **ProfileName** is NULL, the agent profile is disabled. If **ProfileName** is not specified, the default profile for the agent type is used. For information, see [Replication Agent Profiles](../../../relational-databases/replication/agents/replication-agent-profiles.md).