Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into GHI

Author: markingmyname

docs/big-data-cluster/deploy-offline.md

@@ -49,6 +49,10 @@ The following steps describe how to pull the big data cluster container images f
    ```PowerShell
    docker push <TARGET_DOCKER_REGISTRY>/<TARGET_DOCKER_REPOSITORY>/<SOURCE_IMAGE_NAME>:<TARGET_DOCKER_TAG>
    ```
+ 
+> [!WARNING]
+> Do not modify the big data cluster images once they are pushed into your private repository. Performing a deployment with modified images will result in an unsupported big data cluster setup.
+
 
 ### <a id="images"></a> Big data cluster container images
 

docs/database-engine/availability-groups/windows/enhanced-database-failover.md

@@ -2,9 +2,8 @@
 title: "Enhanced failover for an availability group"
 description: "Steps to enable enhanced database failover, which triggers a failover if a database in an Always On availability group is no longer able to write transactions."
 ms.custom: "seodec18"
-ms.date: "09/25/2017"
+ms.date: 06/03/2020
 ms.prod: sql
-ms.reviewer: ""
 ms.technology: high-availability
 ms.topic: conceptual
 helpviewer_keywords: 

docs/machine-learning/install/sql-r-services-windows-install.md

@@ -1,17 +1,20 @@
 ---
 title: Known issues for Python and R
+description: This article describes known problems or limitations with the Python and R components that are provided in SQL Server Machine Learning Services and SQL Server 2016 R Services.
 ms.prod: sql
 ms.technology: machine-learning
-ms.date: 04/06/2020
+ms.date: 06/03/2020
 ms.topic: conceptual
+#ms.topic: troubleshooting
 author: dphansen
 ms.author: davidph
+ms.custom: contperfq4
 monikerRange: ">=sql-server-2016||>=sql-server-linux-ver15||=sqlallproducts-allversions"
 ---
 # Known issues in SQL Server Machine Learning Services
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
 
-This article describes known problems or limitations with machine learning components that are provided as an option in [SQL Server Machine Learning Services](sql-server-machine-learning-services.md) and [SQL Server 2016 R Services](r/sql-server-r-services.md).
+This article describes known problems or limitations with the Python and R components that are provided in [SQL Server Machine Learning Services](sql-server-machine-learning-services.md) and [SQL Server 2016 R Services](r/sql-server-r-services.md).
 
 ## Setup and configuration issues
 

docs/machine-learning/known-issues-for-sql-server-machine-learning-services.md

@@ -1,30 +1,29 @@
 ---
-title: Grant permissions for scripts
-description: How to grant database user permissions for R and Python script execution on SQL Server Machine Learning Services.
+title: Grant permissions to execute Python and R scripts
+description: Learn how you can give users permission to run external Python and R scripts in SQL Server Machine Learning Services and give read, write, or data definition language (DDL) permissions to databases.
 ms.prod: sql
 ms.technology: machine-learning
-
-ms.date: 10/17/2018  
+ms.date: 06/03/2020
 ms.topic: conceptual
 author: dphansen
 ms.author: davidph
-ms.custom: seo-lt-2019
+ms.custom: seo-lt-2019, contperfq4
 monikerRange: ">=sql-server-2016||>=sql-server-linux-ver15||=sqlallproducts-allversions"
 ---
-# Give users permission to SQL Server Machine Learning Services
+# Grant users permission to execute Python and R scripts with SQL Server Machine Learning Services
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
 
-This article describes how you can give users permission to run external scripts in SQL Server Machine Learning Services and give read, write, or data definition language (DDL) permissions to databases.
+Learn how you can give users permission to run external Python and R scripts in [SQL Server Machine Learning Services](../sql-server-machine-learning-services.md) and give read, write, or data definition language (DDL) permissions to databases.
 
 For more information, see the permissions section in [Security overview for the extensibility framework](../../machine-learning/concepts/security.md#permissions).
 
 <a name="permissions-external-script"></a>
 
 ## Permission to run scripts
 
-If you installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] yourself, and you are running R or Python scripts in your own instance, you typically execute scripts as an administrator. Thus, you have implicit permission over various operations and all data in the database.
+For each user who runs Python or R scripts with SQL Server Machine Learning Services, and who are not an administrator, you must grant them the permission to run external scripts in each database where the language is used.
 
-Most users, however, do not have such elevated permissions. For example, users in an organization who use SQL logins to access the database generally do not have elevated permissions. Therefore, for each user who is using R or Python, you must grant users of Machine Learning Services the permission to run external scripts in each database where the language is used. Here's how:
+To grant permission to execute external script, run the following script:
 
 ```sql
 USE <database_name>
@@ -33,15 +32,19 @@ GRANT EXECUTE ANY EXTERNAL SCRIPT TO [UserName]
 ```
 
 > [!NOTE]
-> Permissions are not specific to the supported script language. In other words, there are not separate permission levels for R script versus Python script. If you need to maintain separate permissions for these languages, install R and Python on separate instances.
+> Permissions are not specific to the supported script language. In other words, there are not separate permission levels for R script versus Python script.
 
-<a name="permissions-db"></a> 
+<a name="permissions-db"></a>
 
 ## Grant databases permissions
 
 While a user is running scripts, the user might need to read data from other databases. The user might also need to create new tables to store results, and write data into tables.
 
-For each Windows user account or SQL login that is running R or Python scripts, ensure that it has the appropriate permissions on the specific database:  `db_datareader` to read data, `db_datawriter` to save objects to the database, or `db_ddladmin` to create objects such as stored procedures or tables containing trained and serialized data.
+For each Windows user account or SQL login that is running R or Python scripts, ensure that it has the appropriate permissions on the specific database: 
+
++ `db_datareader` to read data.
++ `db_datawriter` to save objects to the database.
++ `db_ddladmin` to create objects such as stored procedures or tables containing trained and serialized data.
 
 For example, the following [!INCLUDE[tsql](../../includes/tsql-md.md)] statement gives the SQL login *MySQLLogin* the rights to run T-SQL queries in the *ML_Samples* database. To run this statement, the SQL login must already exist in the security context of the server.
 
@@ -53,4 +56,4 @@ EXEC sp_addrolemember 'db_datareader', 'MySQLLogin'
 
 ## Next steps
 
-For more information about the permissions included in each role, see [Database-level roles](../../relational-databases/security/authentication-access/database-level-roles.md).
+For more information about the permissions included in each role, see [Database-level roles](../../relational-databases/security/authentication-access/database-level-roles.md).

docs/machine-learning/security/user-permission.md

@@ -1,7 +1,7 @@
 ---
 title: "Dynamic SQL | Microsoft Docs"
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: "06/03/2020"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -33,4 +33,4 @@ Although static SQL works well in many situations, there is a class of applicati
 
 3.  The program can use the EXECUTE statement repeatedly, supplying different parameter values each time the dynamic statement is executed.  
 
- Prepared execution is still not the same as static SQL. In static SQL, the first four steps of processing an SQL statement take place at compile time. In prepared execution, these steps still take place at run time, but they are performed only once; execution of the plan takes place only when EXECUTE is called. This helps eliminate some of the performance disadvantages inherent in the architecture of dynamic SQL. The next illustration shows the differences between static SQL, dynamic SQL with immediate execution, and dynamic SQL with prepared execution.
+ Prepared execution is still not the same as static SQL. In static SQL, the first four steps of processing an SQL statement take place at compile time. In prepared execution, these steps still take place at run time, but they are performed only once; execution of the plan takes place only when EXECUTE is called. This helps eliminate some of the performance disadvantages inherent in the architecture of dynamic SQL.

docs/odbc/reference/dynamic-sql.md

@@ -1,7 +1,6 @@
 ---
 title: "Add Collection Item to Collection Set (T-SQL)"
-ms.custom: ""
-ms.date: "03/07/2017"
+ms.date: 06/03/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: supportability
@@ -25,13 +24,15 @@ ms.custom: "seo-lt-2019"
 1.  Stop the collection set that you want to add the item to by running the **sp_syscollector_stop_collection_set** stored procedure. For example, to stop a collection set that is named "Test Collection Set", run the following statements:  
 
     ```sql  
-    USE msdb  
-    DECLARE @csid int  
+    USE msdb;
+    DECLARE @csid int;
+
     SELECT @csid = collection_set_id  
-    FROM syscollector_collection_sets  
-    WHERE name = 'Test Collection Set'  
-    SELECT @csid  
-    EXEC dbo.sp_syscollector_stop_collection_set @collection_set_id = @csid  
+      FROM syscollector_collection_sets
+      WHERE name = 'Test Collection Set';
+
+    SELECT @csid;
+    EXEC dbo.sp_syscollector_stop_collection_set @collection_set_id = @csid;
     ```  
 
     > [!NOTE]  
@@ -40,53 +41,60 @@ ms.custom: "seo-lt-2019"
 2.  Declare the collection set that you want to add the collection item to. The following code provides an example of how to declare the collection set ID.  
 
     ```sql  
-    DECLARE @collection_set_id_1 int  
-    SELECT @collection_set_id_1 = collection_set_id FROM [msdb].[dbo].[syscollector_collection_sets]  
-    WHERE name = N'Test Collection Set'; -- name of collection set  
+    DECLARE @collection_set_id_1 int;
+
+    SELECT @collection_set_id_1 = collection_set_id
+      FROM [msdb].[dbo].[syscollector_collection_sets]
+      WHERE name = N'Test Collection Set'; -- name of collection set  
     ```  
 
 3.  Declare the collector type. The following code provides an example of how to declare the Generic T-SQL Query collector type.  
 
     ```sql  
-    DECLARE @collector_type_uid_1 uniqueidentifier  
-    SELECT @collector_type_uid_1 = collector_type_uid FROM [msdb].[dbo].[syscollector_collector_types]   
+    DECLARE @collector_type_uid_1 uniqueidentifier;
+
+    SELECT @collector_type_uid_1 = collector_type_uid
+       FROM [msdb].[dbo].[syscollector_collector_types]
        WHERE name = N'Generic T-SQL Query Collector Type';  
     ```  
 
      You can run the following code to obtain a list of the installed collector types:  
 
     ```sql  
-    USE msdb  
-    SELECT * from syscollector_collector_types  
+    USE msdb;
+    SELECT * from syscollector_collector_types;
     GO  
     ```  
 
 4.  Run the **sp_syscollector_create_collection_item** stored procedure to create the collection item. You must declare the schema for the collection item so that it maps to the required schema for the desired collector type. The following example uses the Generic T-SQL Query input schema.  
 
     ```sql  
     DECLARE @collection_item_id int;  
+
     EXEC [msdb].[dbo].[sp_syscollector_create_collection_item]   
-    @name=N'OS Wait Stats', --name of collection item  
-    @parameters=N'  
-    <ns:TSQLQueryCollector xmlns:ns="DataCollectorType">  
-     <Query>  
-      <Value>select * from sys.dm_os_wait_stats</Value>  
-      <OutputTable>os_wait_stats</OutputTable>  
-    </Query>  
-    </ns:TSQLQueryCollector>',  
-    @collection_item_id = @collection_item_id OUTPUT,  
-    @frequency = 60,  
-    @collection_set_id = @collection_set_id_1, --- Provides the collection set ID number  
-    @collector_type_uid = @collector_type_uid_1 -- Provides the collector type UID  
-    SELECT @collection_item_id     
+      @name=N'OS Wait Stats', --name of collection item  
+      @parameters=N'  
+        <ns:TSQLQueryCollector xmlns:ns="DataCollectorType">  
+         <Query>  
+          <Value>select * from sys.dm_os_wait_stats</Value>  
+          <OutputTable>os_wait_stats</OutputTable>  
+        </Query>  
+        </ns:TSQLQueryCollector>',  
+      @collection_item_id = @collection_item_id OUTPUT,  
+      @frequency = 60,  
+      @collection_set_id = @collection_set_id_1, --- Provides the collection set ID number  
+      @collector_type_uid = @collector_type_uid_1; -- Provides the collector type UID  
+    
+    SELECT @collection_item_id;
     ```  
 
 5.  Before starting the updated collection set, run the following query to verify that the new collection item has been created:  
 
-    ```xaml  
-    USE msdb  
-    SELECT * from syscollector_collection_sets  
-    SELECT * from syscollector_collection_items  
+    ```sql
+    USE msdb;
+    GO
+    SELECT * from syscollector_collection_sets;
+    SELECT * from syscollector_collection_items;
     GO  
     ```  
 

docs/relational-databases/data-collection/add-a-collection-item-to-a-collection-set-transact-sql.md

@@ -1,7 +1,6 @@
 ---
 title: "Configure Data Collection Parameters (T-SQL)"
-ms.custom: ""
-ms.date: "03/04/2017"
+ms.date: 06/03/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: supportability

docs/relational-databases/data-collection/configure-data-collection-parameters-transact-sql.md

@@ -1,7 +1,6 @@
 ---
 title: "Create Custom Collection Set - Generic T-SQL Query Collector Type"
-ms.custom: ""
-ms.date: "03/07/2017"
+ms.date: 06/03/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: supportability
@@ -33,10 +32,12 @@ ms.custom: "seo-lt-2019"
 
 1.  Define a new collection set using the sp_syscollector_create_collection_set stored procedure.  
 
-    ```  
+    ```sql
     USE msdb;  
+    GO
     DECLARE @collection_set_id int;  
     DECLARE @collection_set_uid uniqueidentifier;  
+
     EXEC sp_syscollector_create_collection_set   
         @name=N'DMV Test 1',   
         @collection_mode=0,   
@@ -46,6 +47,7 @@ ms.custom: "seo-lt-2019"
         @schedule_name=N'CollectorSchedule_Every_15min',   
         @collection_set_id=@collection_set_id OUTPUT,   
         @collection_set_uid=@collection_set_uid OUTPUT;  
+
     SELECT @collection_set_id, @collection_set_uid;  
     ```  
 
@@ -75,8 +77,11 @@ ms.custom: "seo-lt-2019"
 
     ```sql  
     DECLARE @collector_type_uid uniqueidentifier;  
-    SELECT @collector_type_uid = collector_type_uid FROM [msdb].[dbo].[syscollector_collector_types]   
-    WHERE name = N'Generic T-SQL Query Collector Type';  
+
+    SELECT @collector_type_uid = collector_type_uid
+      FROM [msdb].[dbo].[syscollector_collector_types]   
+      WHERE name = N'Generic T-SQL Query Collector Type';  
+
     DECLARE @collection_item_id int;  
     ```  
 
@@ -96,6 +101,7 @@ ms.custom: "seo-lt-2019"
         @frequency=5,   
         @collection_set_id=@collection_set_id,   
         @collector_type_uid=@collector_type_uid;  
+
     SELECT @collection_item_id;  
     ```  
 
@@ -105,6 +111,7 @@ ms.custom: "seo-lt-2019"
 
     ```sql  
     USE msdb;  
+    GO
     SELECT * FROM syscollector_collection_sets;  
     SELECT * FROM syscollector_collection_items;  
     GO  
@@ -130,28 +137,32 @@ EXEC dbo.sp_syscollector_create_collection_set
     @schedule_name=N'CollectorSchedule_Every_15min',  
     @collection_set_id = @collection_set_id OUTPUT,  
     @collection_set_uid = @collection_set_uid OUTPUT;  
+
 SELECT @collection_set_id,@collection_set_uid;  
   
 DECLARE @collector_type_uid uniqueidentifier;  
-SELECT @collector_type_uid = collector_type_uid FROM syscollector_collector_types   
-WHERE name = N'Generic T-SQL Query Collector Type';  
+
+SELECT @collector_type_uid = collector_type_uid
+  FROM syscollector_collector_types   
+  WHERE name = N'Generic T-SQL Query Collector Type';  
   
 DECLARE @collection_item_id int;  
+
 EXEC sp_syscollector_create_collection_item  
-@name= N'Query Stats - Test 1',  
-@parameters=N'  
-<ns:TSQLQueryCollector xmlns:ns="DataCollectorType">  
-<Query>  
-  <Value>select * from sys.dm_exec_query_stats</Value>  
-  <OutputTable>dm_exec_query_stats</OutputTable>  
-</Query>  
- </ns:TSQLQueryCollector>',  
-    @collection_item_id = @collection_item_id OUTPUT,  
-    @frequency = 5, -- This parameter is ignored in cached mode  
-    @collection_set_id = @collection_set_id,  
-    @collector_type_uid = @collector_type_uid;  
+    @name= N'Query Stats - Test 1',  
+    @parameters=N'  
+    <ns:TSQLQueryCollector xmlns:ns="DataCollectorType">  
+    <Query>  
+      <Value>select * from sys.dm_exec_query_stats</Value>  
+      <OutputTable>dm_exec_query_stats</OutputTable>  
+    </Query>  
+     </ns:TSQLQueryCollector>',  
+        @collection_item_id = @collection_item_id OUTPUT,  
+        @frequency = 5, -- This parameter is ignored in cached mode  
+        @collection_set_id = @collection_set_id,  
+        @collector_type_uid = @collector_type_uid;  
+        
 SELECT @collection_item_id;  
-  
 GO  
 ```