Merge branch 'release-sqlseattle' of

negust-microsoft · negust-microsoft · commit 1410f42b928e · 2018-09-10T18:57:09.000-07:00
diff --git a/docs/advanced-analytics/r/sql-server-r-services.md b/docs/advanced-analytics/r/sql-server-r-services.md
@@ -1,10 +1,10 @@
 ---
 title: R Services in SQL Server 2016 | Microsoft Docs
-description: Overview introduction to SQL Server Services, R support for in-database analytics
+description: R in SQL Server for integrated R tasks on relational data, including data science and statistical modeling, predictive analytics, data visualization and more.
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 08/27/2018  
+ms.date: 09/10/2018  
 ms.topic: overview
 author: HeidiSteen
 ms.author: heidist
@@ -13,12 +13,15 @@ manager: cgronlun
 # R Services in SQL Server 2016
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
 
-SQL Server 2016 R Services is an add-on to a database engine instance, used for executing R code and functions on SQL Server. Code runs in an extensibility framework, isolated from core engine processes, but fully available to relational data as stored procedures, as T-SQL script containing R statements, or as R code containing T-SQL. 
+R Services is an add-on to a SQL Server 2016 database engine instance, used for executing R code and functions on SQL Server. Code runs in an extensibility framework, isolated from core engine processes, but fully available to relational data as stored procedures, as T-SQL script containing R statements, or as R code containing T-SQL. 
 
 R Services includes a base distribution of R, overlaid with enterprise R packages from Microsoft so that you can load and process large amounts of data on multiple cores and aggregate the results into a single consolidated output. Microsoft's R functions and algorithms are engineered for both scale and utility: delivering predictive analytics, statistical modeling, data visualizations, and leading-edge machine learning algorithms in a commercial server product engineered and supported by Microsoft. 
 
 R libraries include RevoScaleR, MicrosoftML, and others. Because R Services is integrated with the database engine, you can keep analytics close to the data and eliminate the costs and security risks associated with data movement.
 
+> [!Note]
+> R Services was renamed in SQL Server 2017 to [SQL Server Machine Learning Services](../what-is-sql-server-machine-learning.md), reflecting the addition of Python.
+
 ## Components
 
 SQL Server 2016 is R only. The following table describes the features in SQL Server 2016.
@@ -36,7 +39,7 @@ SQL Server 2016 is R only. The following table describes the features in SQL Ser
 
 Developers and analysts often have code running on top of a local SQL Server instance. By adding Machine Learning Services and enabling external script execution, you gain the ability to run R code in SQL Server modalities: wrapping script in stored procedures, storing models in a SQL Server table, or combining T-SQL and R functions in queries.
 
-The most common approach for in-database analytics is to use [sp_execute_external_script](../../relational-databases/system-stored-procedures/sp-execute-external-script-transact-sql.md), passing Rscript as an input parameter.
+The most common approach for in-database analytics is to use [sp_execute_external_script](../../relational-databases/system-stored-procedures/sp-execute-external-script-transact-sql.md), passing R script as an input parameter.
 
 Classic client-server interactions are another approach. From any client workstation that has an IDE, you can install [Microsoft R Client](https://docs.microsoft.com/machine-learning-server/r-client/what-is-microsoft-r-client), and then write code that pushes execution (referred to as a *remote compute context*) to data and operations to a remote SQL Server. 
 
diff --git a/docs/advanced-analytics/tutorials/deepdive-data-science-deep-dive-using-the-revoscaler-packages.md b/docs/advanced-analytics/tutorials/deepdive-data-science-deep-dive-using-the-revoscaler-packages.md
@@ -69,7 +69,7 @@ You should also be comfortable with [!INCLUDE[tsql](../../includes/tsql-md.md)]
 
 R developers typically use IDEs for writing and debugging R code. Here are some suggestions:
 
-- **R Tools for Visual Studio** (RTVS) is a free plug-in that provides Intellisense, debugging, and support for Microsoft R. YOu can use it with both R Server and SQL Server Machine Learning Services. To download, see [R Tools for Visual Studio](https://www.visualstudio.com/vs/rtvs/).
+- **R Tools for Visual Studio** (RTVS) is a free plug-in that provides Intellisense, debugging, and support for Microsoft R. You can use it with both R Server and SQL Server Machine Learning Services. To download, see [R Tools for Visual Studio](https://www.visualstudio.com/vs/rtvs/).
 
 - **RStudio** is one of the more popular environments for R development. For more information, see [https://www.rstudio.com/products/RStudio/](https://www.rstudio.com/products/RStudio/).
 
diff --git a/docs/advanced-analytics/what-is-sql-server-machine-learning.md b/docs/advanced-analytics/what-is-sql-server-machine-learning.md
@@ -1,21 +1,21 @@
 ---
-title: Machine Learning Services in SQL Server | Microsoft Docs
-description: Overview introduction to SQL Server 2017 Machine Learning Services, R and Python support for in-database analytics
+title: R and Python Machine Learning Services in SQL Server | Microsoft Docs
+description: R in SQL Server and Python in SQL Server, integrating with relational data for data science and statistical modeling, machine learning models, predictive analytics, data visualization and more.
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 08/27/2018  
+ms.date: 09/10/2018  
 ms.topic: overview
 author: HeidiSteen
 ms.author: heidist
 manager: cgronlun
 ---
-# Machine Learning Services in SQL Server 2017
+# Machine Learning Services (R, Python) in SQL Server 2017
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
 
 SQL Server 2017 Machine Learning Services is an add-on to a database engine instance, used for executing R and Python code on SQL Server. Code runs in an extensibility framework, isolated from core engine processes, but fully available to relational data as stored procedures, as T-SQL script containing R or Python statements, or as R or Python code containing T-SQL. 
 
-If you previously used SQL Server 2016 R Services, Machine Learning Services in SQL Server 2017 is the next generation of R support, with updated versions of base R, RevoScaleR, MicrosoftML, and other libraries introduced in 2016.
+If you previously used [SQL Server 2016 R Services](r/sql-server-r-services.md), Machine Learning Services in SQL Server 2017 is the next generation of R support, with updated versions of base R, RevoScaleR, MicrosoftML, and other libraries introduced in 2016.
 
 The key value proposition of Machine Learning Services is the power of its enterprise R and Python packages to deliver advanced analytics at scale, and the ability to bring calculations and processing to where the data resides, eliminating the need to pull data across the network.
 
diff --git a/docs/analytics-platform-system/appliance-feature-switch.md b/docs/analytics-platform-system/appliance-feature-switch.md
@@ -11,13 +11,16 @@ ms.author: "murshedz"
 ms.reviewer: "martinle"
 monikerRange: ">= aps-pdw-2016-au7 || = sqlallproducts-allversions"
 ---
-#Appliance Feature Switch
-The **Feature Switch** page displays information about the two feature switches that are introduced in Analytics Platform System 2016-AU7. Use this page to update or enable/disable features and settings in Analytics Platform System. Changing feature switch values requires a service restart.
+#Appliance Feature Switches
+The **Feature Switch** page displays information about the feature switches that are being introduced in Analytics Platform System AU7 and later. Use this configuration page to update or enable/disable features and settings in Analytics Platform System. Changes to feature switch values require a service restart.
 
 ![DWConig Appliance Feature Switch](media/feature-switch/SQL_Server_PDW_DWConfig_feature_switch.png "DWConig Appliance Feature Switch") 
 
-##AutoStatsEnabled Switch
+##AutoStatsEnabled
 Controls the auto statistics feature. This feature switch is set to true by default after upgrading to AU7. Any database created after the upgrade will inherit auto creation and asynchronous update of statistics. For existing databases, database administrators can enable auto statistics with [ALTER DATABASE (Parallel Data Warehouse)](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw). For more information on statistics, see [Statistics](../relational-databases/statistics/statistics.md).
 
-##DmsProcessStopMessageTimeoutInSeconds Switch
+##UseCatalogQueries
+Using catalog objects for some metadata calls instead of using SMO has shown performance improvement. Set to true by default in CU7.1, this switch controls that behavior. 
+
+##DmsProcessStopMessageTimeoutInSeconds
 Controls the time Data Movement Service (DMS) waits to synchronize on a busy system when a query involving data movement is cancelled. Updating to AU7 sets this value to 900 seconds (15 minutes) by default. The valid range is 0 – 3600 seconds.
diff --git a/docs/analytics-platform-system/media/feature-switch/SQL_Server_PDW_DWConfig_feature_switch.png b/docs/analytics-platform-system/media/feature-switch/SQL_Server_PDW_DWConfig_feature_switch.png
diff --git a/docs/connect/odbc/using-always-encrypted-with-the-odbc-driver.md b/docs/connect/odbc/using-always-encrypted-with-the-odbc-driver.md
@@ -1,10 +1,8 @@
 ---
 title: "Using Always Encrypted with the ODBC Driver for SQL Server | Microsoft Docs"
 ms.custom: ""
-ms.date: "10/01/2018"
+ms.date: 09/01/2018
 ms.prod: sql
-ms.prod_service: connectivity
-ms.reviewer: ""
 ms.suite: "sql"
 ms.technology: connectivity
 ms.tgt_pltfrm: ""
diff --git a/docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md b/docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md
@@ -1,7 +1,7 @@
 ---
 title: "Replication, Change Tracking, & Change Data Capture - Availability Groups | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/25/2018"
+ms.date: "08/21/2018"
 ms.prod: sql
 ms.reviewer: ""
 ms.suite: "sql"
@@ -39,7 +39,7 @@ manager: craigg
 ###  <a name="Changes"></a> General changes to replication agents to support availability groups  
  Three replication agents were modified to support [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. The Log Reader, Snapshot, and Merge agents were modified to query the distribution database for the redirected publisher and to use the returned availability group listener name, if a redirected publisher was declared, to connect to the database publisher.  
   
- By default, when the agents query the distributor to determine whether the original publisher has been redirected, the suitability of the current target or redirection will be verified prior to returning the redirected host to the agent. This is recommended behavior. However, if agent start up occurs very frequently the overhead associated with the validation stored procedure may be deemed too costly. A new command line switch, *BypassPublisherValidation*, has been added to the Logreader, Snapshot, and Merge agents. When the switch is used, the redirected publisher is returned immediately to the agent and execution of the validation stored procedure is bypassed.  
+ By default, when the agents query the distributor to determine whether the original publisher has been redirected, the suitability of the current target or redirection will be verified prior to returning the redirected host to the agent. This is recommended behavior. However, if agent startup occurs very frequently the overhead associated with the validation stored procedure may be deemed too costly. A new command-line switch, *BypassPublisherValidation*, has been added to the Logreader, Snapshot, and Merge agents. When the switch is used, the redirected publisher is returned immediately to the agent and execution of the validation stored procedure is bypassed.  
   
  Failures returned from the validation stored procedure are logged in the agent history logs. Those errors with severity greater than or equal to 16 will cause the agents to terminate. Some retry capabilities have been built in to the agents to handle the expected disconnect from a published database when it fails over to a new primary.  
   
@@ -54,7 +54,7 @@ manager: craigg
   
 -   **Trace flag 1448**  
   
-     Trace flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas have not acknowledged the reception of a change. Even with this trace flag enabled,, the log reader always waits for the synchronous secondary replicas. The log reader will not go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], not just to an availability group, an availability database, or a log reader instance. This trace flag takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.  
+     Trace flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas have not acknowledged the reception of a change. Even with this trace flag enabled, the log reader always waits for the synchronous secondary replicas. The log reader will not go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], not just to an availability group, an availability database, or a log reader instance. This trace flag takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.  
   
 ###  <a name="StoredProcs"></a> Stored procedures supporting availability groups  
   
@@ -137,9 +137,9 @@ manager: craigg
   
 -   **Redirecting the Query Load to a Readable Secondary Replica**  
   
-     While in many cases a client application will always want to connect to the current primary replica that is not the only way to leverage [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. If an availability group is configured to support readable secondary replicas, change data can also be gathered from secondary nodes.  
+     While in many cases a client application will always want to connect to the current primary replica, that is not the only way to leverage [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. If an availability group is configured to support readable secondary replicas, change data can also be gathered from secondary nodes.  
   
-     When an availability group is configured, the ALLOW_CONNECTIONS attribute associated with the SECONDARY_ROLE is used to specify the type of secondary access supported. If configured as ALL, all connections to the secondary will be allowed, but only those requiring read only access will succeed. If configured as READ_ONLY, it is necessary to specify read only intent when making the connection to the secondary database in order for the connection to succeed. For more information, see [Configure Read-Only Access on an Availability Replica &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server.md).  
+     When an availability group is configured, the ALLOW_CONNECTIONS attribute associated with the SECONDARY_ROLE is used to specify the type of secondary access supported. If configured as ALL, all connections to the secondary will be allowed, but only those requiring read-only access will succeed. If configured as READ_ONLY, it is necessary to specify read only intent when making the connection to the secondary database in order for the connection to succeed. For more information, see [Configure Read-Only Access on an Availability Replica &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server.md).  
   
      The following query can be used to determine whether read-only intent is needed to connect to a readable secondary replica.  
   
@@ -205,12 +205,10 @@ If Change Data Capture needs to be disabled on a database which is part of an Al
 |||||  
 |-|-|-|-|  
 ||**Publisher**|**Distributor***\*|**Subscriber**|  
-|**Transactional**|Yes<br /><br /> Note: Does not include support for bi-directional and reciprocal transactional replication.|No|Yes|  
+|**Transactional**|Yes<br /><br /> Note: Does not include support for bi-directional and reciprocal transactional replication.|Yes|Yes| 
 |**P2P**|No|No|No|  
-|**Merge**|Yes|No|Yes*|  
-|**Snapshot**|Yes|No|Yes*|  
-  
- *Failover to the replica database is a manual procedure. Automatic failover is not provided.  
+|**Merge**|Yes|No|No|  
+|**Snapshot**|Yes|No|Yes|
   
  **The Distributor database is not supported for use with database mirroring.  
   
diff --git a/docs/index.md b/docs/index.md
@@ -3,6 +3,7 @@ layout: HubPage
 hide_bc: true
 title: Microsoft SQL Documentation | Microsoft Docs
 description: Learn about SQL
+ms.date: 09/01/2018
 author: craigg-msft 
 ms.author: craigg
 ms.topic: conceptual
diff --git a/docs/relational-databases/databases/model-database.md b/docs/relational-databases/databases/model-database.md
@@ -43,7 +43,7 @@ manager: craigg
 |Primary data|modeldev|model.mdf|Autogrow by 64 MB until the disk is full.|  
 |Log|modellog|modellog.ldf|Autogrow by 64 MB to a maximum of 2 terabytes.|  
   
- For versions before [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)], see [model Database](model-database.md)for default file growth values.  
+ For versions before [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)], see [model Database](../../2014/relational-databases/databases/model-database.md) for default file growth values.  
   
  To move the **model** database or log files, see [Move System Databases](../../relational-databases/databases/move-system-databases.md).  
   
diff --git a/docs/relational-databases/polybase/data-virtualization.md b/docs/relational-databases/polybase/data-virtualization.md
diff --git a/docs/sql-server/what-s-new-in-sql-server-ver15.md b/docs/sql-server/what-s-new-in-sql-server-ver15.md
