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

Author: dksimpson

docs/analytics-platform-system/configure-polybase-connectivity-to-external-data.md

@@ -11,7 +11,7 @@ ms.reviewer: martinle
 ms.custom: seo-dt-2019
 ---
 
-# What is PolyBase?
+# Configure PolyBase connectivity
 PolyBase enables your Analytics Platform System (APS) to process Transact-SQL queries that can read data from and write data to external data sources. The same queries that access external data can also include relation tables in your APS. This allows you to combine data from external sources with high-value relational data in your APS databases.
 
 ![PolyBase logical](media/polybase/polybase-logical.png)

docs/big-data-cluster/deploy-active-directory.md

@@ -176,15 +176,20 @@ AD integration requires the following parameters. Add these parameters to the `c
 
 - `security.activeDirectory.realm` **Optional parameter**: In the majority of cases, the realm equals domain name. For cases where they are not the same, use this parameter to define name of realm (e.g. `CONTOSO.LOCAL`). The value of provided for this parameter should be fully-qualified.
 
-- `security.activeDirectory.domainDnsName`: Name of your DNS domain that will be used for the cluster (e.g. `contoso.local`). 
+- `security.activeDirectory.domainDnsName`: Name of your DNS domain that will be used for the cluster (e.g. `contoso.local`).
 
-- `security.activeDirectory.clusterAdmins`: This parameter takes one AD group. The AD group scope must be universal or global. Members of this group get administrator permissions in the cluster. This means that they have `sysadmin` permissions in SQL Server, superuser permissions in HDFS, and administrators in controller. 
+- `security.activeDirectory.clusterAdmins`: This parameter takes one AD group. The AD group scope must be universal or global. Members of this group will have the *bdcAdmin* cluster role which will give them administrator permissions in the cluster. This means that they have [`sysadmin` permissions in SQL Server](../relational-databases/security/authentication-access/server-level-roles.md#fixed-server-level-roles), [`superuser` permissions in HDFS](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsPermissionsGuide.html#The_Super-User), and admin permissions when connected to the controller endpoint.
 
   >[!IMPORTANT]
   >Create this group in AD before deployment begins. If the scope for this AD group is domain local deployment fails.
 
 - `security.activeDirectory.clusterUsers`: List of the AD groups that are regular users (no administrator permissions) in the big data cluster. The list can include AD groups that are scoped as either universal or global groups. They cannot be domain local groups.
 
+AD groups in this list are mapped to the *bdcUser* big data cluster role and they need to be granted access to SQL Server (see [SQL Server permissions](../relational-databases/security/permissions-hierarchy-database-engine.md)) or HDFS (see [HDFS permissions Guide](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsPermissionsGuide.html#:~:text=Permission%20Checks%20%20%20%20Operation%20%20,%20%20N%2FA%20%2029%20more%20rows%20)). When connected to the controller endpoint, these users can only list the endpoints available in the cluster using *azdata bdc endpoint list* command.
+
+For details on how to update the AD groups for this settings see [Manage Big Data Cluster access in Active Directory
+mode](manage-user-access.md).
+
   >[!IMPORTANT]
   >Create these groups in AD before deployment begins. If the scope for any of these AD groups is domain local deployment fails.
 
@@ -222,15 +227,23 @@ AD integration requires the following parameters. Add these parameters to the `c
 }
 ```
 
-- `security.activeDirectory.appOwners` **Optional parameter**: List of AD groups who have permissions to create, delete, and run any application. The list can include AD groups that are scoped as either universal or global groups. They cannot be domain local groups.
-
   >[!IMPORTANT]
-  >Create these groups in AD before deployment begins. If the scope for any of these AD groups is domain local deployment fails.
+  >Create the groups provided for the settings bellow in AD before deployment begins. If the scope for any of these AD groups is domain local deployment fails.
+
+- `security.activeDirectory.appOwners` **Optional parameter**: List of AD groups who have permissions to create, delete, and run any application. The list can include AD groups that are scoped as either universal or global groups. They cannot be domain local groups.
 
 - `security.activeDirectory.appReaders` **Optional parameter**: List of the AD groups who have permissions to run any application. The list can include AD groups that are scoped as either universal or global groups. They cannot be domain local groups.
 
-  >[!IMPORTANT]
-  >Create these groups in AD before deployment begins. If the scope for any of these AD groups is domain local deployment fails.
+Below table show the authorization model for application management:
+
+|   Authorized roles   |   azdata command   |
+|----------------------|--------------------|
+|   appOwner           | azdata app create  |
+|   appOwner           | azdata app update  |
+|   appOwner, appReader| azdata app list    |
+|   appOwner, appReader| azdata app describe|
+|   appOwner           | azdata app delete  |
+|   appOwner, appReader| azdata app run     |
 
 - `security.activeDirectory.subdomain`: **Optional parameter** This parameter is introduced in SQL Server 2019 CU5 release to support deploying multiple big data clusters against the same domain. Using this setting, you can specify different DNS names for each of the big data cluster deployed. If the value of this parameter is not specified in the active directory section of the `control.json` file, by default, the big data cluster name (same as Kubernetes namespace name) will be used to compute the value of subdomain setting. 
 

docs/connect/jdbc/reference/getobject-method-java-lang-string-java-util-map-sqlserverresultset.md

@@ -1,5 +1,5 @@
 ---
-title: "getObject Method (java.lang.String, java.util.Map) | Microsoft Docs"
+title: "getObject Method (java.lang.String, java.util.Map) (SQLServerResultSet) | Microsoft Docs"
 ms.custom: ""
 ms.date: "01/19/2017"
 ms.prod: sql

docs/connect/jdbc/reference/gettime-method-java-lang-string-java-util-calendar-sqlserverresultset.md

@@ -1,5 +1,5 @@
 ---
-title: "getTime Method (java.lang.String, java.util.Calendar) | Microsoft Docs"
+title: "getTime Method (java.lang.String, java.util.Calendar) (SQLServerResultSet) | Microsoft Docs"
 ms.custom: ""
 ms.date: "01/19/2017"
 ms.prod: sql

docs/connect/jdbc/reference/gettimestamp-method-int-java-util-calendar-sqlserverresultset.md

@@ -1,5 +1,5 @@
 ---
-title: "getTimestamp Method (int, java.util.Calendar) | Microsoft Docs"
+title: "getTimestamp Method (int, java.util.Calendar) (SQLServerResultSet) | Microsoft Docs"
 ms.custom: ""
 ms.date: "01/19/2017"
 ms.prod: sql

docs/connect/jdbc/reference/gettimestamp-method-java-lang-string-java-util-calendar-sqlserverresultset.md

@@ -1,5 +1,5 @@
 ---
-title: "getTimestamp Method (java.lang.String, java.util.Calendar) | Microsoft Docs"
+title: "getTimestamp Method (java.lang.String, java.util.Calendar) (SQLServerResultSet) | Microsoft Docs"
 ms.custom: ""
 ms.date: "01/19/2017"
 ms.prod: sql

docs/connect/oledb/ole-db-blobs/getting-large-data.md

@@ -1,5 +1,5 @@
 ---
-title: "Getting Large Data | Microsoft Docs"
+title: "Getting large data (OLE DB driver) | Microsoft Docs"
 description: "Getting large data using OLE DB Driver for SQL Server"
 ms.custom: ""
 ms.date: "06/14/2018"

docs/connect/oledb/ole-db-data-source-objects/initialization-and-authorization-properties.md

@@ -1,5 +1,5 @@
 ---
-title: "Initialization and Authorization Properties | Microsoft Docs"
+title: "Initialization and authorization properties (OLE DB driver) | Microsoft Docs"
 description: "Initialization and authorization properties"
 ms.custom: ""
 ms.date: "01/02/2020"

docs/connect/oledb/ole-db-date-time/data-type-support-for-ole-db-date-and-time-improvements.md

@@ -1,5 +1,5 @@
 ---
-title: "Data Type Support for OLE DB Date and Time Improvements | Microsoft Docs"
+title: "Data type support for date and time improvements (OLE DB driver) | Microsoft Docs"
 description: "Data type support for OLE DB date and time improvements"
 ms.custom: ""
 ms.date: "06/14/2018"
@@ -69,7 +69,7 @@ ms.author: pelopes
 
  Implementations for the following existing OLE DB structs have been modified to support the new [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] date and time data types. The definitions, however, have not changed.  
 
--   DBTYPE_DATE (This is an automation DATE type. It is internally represented as a **double**.. The whole part is the number of days since December 30, 1899 and the fractional part is the fraction of a day. This type has an accuracy of 1 second, so has an effective scale of 0.)  
+-   DBTYPE_DATE (This is an automation DATE type. It is internally represented as a **double**. The whole part is the number of days since December 30, 1899 and the fractional part is the fraction of a day. This type has an accuracy of 1 second, so has an effective scale of 0.)  
 
 -   DBTYPE_DBDATE  
 

docs/connect/oledb/ole-db-driver/establishing-a-connection-to-a-data-source.md

@@ -1,5 +1,5 @@
 ---
-title: "Establishing a Connection to a Data Source | Microsoft Docs"
+title: "Establish connection to data source (OLE DB driver) | Microsoft Docs"
 description: "Establishing a connection to a data source using OLE DB Driver for SQL Server"
 ms.custom: ""
 ms.date: "06/14/2018"