Merge pull request #14185 from MicrosoftDocs/master

huypub · web-flow · commit a17245869c2d · 2020-03-17T15:30:22.000-07:00
3/17 PM Publish
diff --git a/docs/2014/includes/media/yes.png b/docs/2014/includes/media/yes.png
diff --git a/docs/big-data-cluster/deploy-active-directory.md b/docs/big-data-cluster/deploy-active-directory.md
@@ -73,19 +73,19 @@ The BDC domain service account (DSA) needs to be able to create users, groups, a
 
     ![image15](./media/deploy-active-directory/image15.png)
 
-1. Click **Add...** and add the **[!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)]DSA** user
+1. Click **Add...** and add the **bdcDSA** user
 
     ![image16](./media/deploy-active-directory/image16.png)
 
     ![image17](./media/deploy-active-directory/image17.png)
 
-1. Select the **[!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)]DSA** user and clear all permissions, then click **Advanced**
+1. Select the **bdcDSA** user and clear all permissions, then click **Advanced**
 
 1. Click **Add**
 
     ![image18](./media/deploy-active-directory/image18.png)
 
-    - Click **Select a Principal**, insert **[!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)]DSA**, and click Ok
+    - Click **Select a Principal**, insert **bdcDSA**, and click Ok
 
     - Set **Type** to **Allow**
 
@@ -109,7 +109,7 @@ The BDC domain service account (DSA) needs to be able to create users, groups, a
 
 - Click **Add**
 
-    - Click **Select a Principal**, insert **[!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)]DSA**, and click Ok
+    - Click **Select a Principal**, insert **bdcDSA**, and click Ok
 
     - Set **Type** to **Allow**
 
@@ -123,7 +123,7 @@ The BDC domain service account (DSA) needs to be able to create users, groups, a
 
 - Click **Add**
 
-    - Click **Select a Principal**, insert **[!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)]DSA**, and click Ok
+    - Click **Select a Principal**, insert **bdcDSA**, and click Ok
 
     - Set **Type** to **Allow**
 
@@ -162,7 +162,7 @@ AD integration requires the following parameters. Add these parameters to the `c
 
 - `security.activeDirectory.ouDistinguishedName`: distinguished name of an organizational unit (OU) where all AD accounts created by cluster deployment will be added. If the domain is called `contoso.local`, the OU distinguished name is: `OU=BDC,DC=contoso,DC=local`.
 
-- `security.activeDirectory.dnsIpAddresses`: list of IP addresses of domain controllers
+- `security.activeDirectory.dnsIpAddresses`: contains the list of domain’s DNS servers IP addresses. 
 
 - `security.activeDirectory.domainControllerFullyQualifiedDns`: List of FQDN of domain controller. The FQDN contains the machine/host name of the domain controller. If you have multiple domain controllers, you can provide a list here. Example: `HOSTNAME.CONTOSO.LOCAL`
 
@@ -246,7 +246,7 @@ You can find an example script here for [deploying a SQL Server big data cluster
 
 You should now have set all the required parameters for a deployment of BDC with Active Directory integration.
 
-For full documentation of how to deploy [!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)], please visit the [official documentation](deployment-guidance.md).
+You can now deploy the BDC cluster integrated with Active Directory using the `azdata` command and the kubeadm-prod deployment profile. For full documentation of how to deploy [!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)], please visit the [How to deploy SQL Server Big Data Clusters on Kubernetes](deployment-guidance.md).
 
 ## Verify reverse DNS entry for domain controller
 
@@ -321,3 +321,5 @@ curl -k -v --negotiate -u : https://<Gateway DNS name>:30443/gateway/default/web
 - Only one BDC per domain (Active Directory) is allowed at this time. Enabling multiple BDCs per domain is planned for a future release.
 
 - None of the AD groups specified in security configurations can be DomainLocal scoped. You can check the scope of an AD group by following [these instructions](https://docs.microsoft.com/powershell/module/activedirectory/get-adgroup?view=winserver2012-ps&viewFallbackFrom=winserver2012r2-ps).
+
+- AD account that can be used to login into BDC are allowed from the same domain that was configured for BDC, Enabling logins from other trusted domain is planned for a future release
diff --git a/docs/big-data-cluster/spark-mssql-connector.md b/docs/big-data-cluster/spark-mssql-connector.md
@@ -15,22 +15,51 @@ ms.technology: big-data-cluster
 
 A key big data usage pattern is high volume data processing in Spark, followed by writing the data to SQL Server for access to line-of-business applications. These usage patterns benefit from a connector that utilizes key SQL optimizations and provides an efficient write mechanism.
 
-This article provides an example of how to use the MSSQL Spark connector to read and write to the following locations within a big data cluster:
-
+This article provides an overview of the MSSQL Spark connector interface and instantiating it for use with non-AD mode and AD-mode. Then, provides an example of how to use the MSSQL Spark connector to read and write to the following locations within a big data cluster:
 1. The SQL Server master instance
 1. The SQL Server data pool
 
    ![MSSQL Spark connector diagram](./media/spark-mssql-connector/mssql-spark-connector-diagram.png)
 
-The sample performs the following tasks:
-
-- Read a file from HDFS and do some basic processing.
-- Write the dataframe to a SQL Server master instance as a SQL table and then read the table to a dataframe.
-- Write the dataframe to a SQL Server data pool as a SQL external table and then read the external table to a dataframe.
-
 ## MSSQL Spark Connector Interface
 
-SQL Server 2019 provides the **MSSQL Spark connector** for big data clusters that uses SQL Server bulk write APIs for Spark to SQL writes. MSSQL Spark Connector is based on Spark data source APIs and provides a familiar Spark JDBC connector interface. For interface parameters refer [Apache Spark documentation](http://spark.apache.org/docs/latest/sql-data-sources-jdbc.html). The MSSQL Spark connector is referenced by the name **com.microsoft.sqlserver.jdbc.spark**.
+SQL Server 2019 provides the **MSSQL Spark connector** for big data clusters that uses SQL Server bulk write APIs for Spark to SQL writes. MSSQL Spark Connector is based on Spark data source APIs and provides a familiar Spark JDBC connector interface. For interface parameters refer [Apache Spark documentation](http://spark.apache.org/docs/latest/sql-data-sources-jdbc.html). The MSSQL Spark connector is referenced by the name **com.microsoft.sqlserver.jdbc.spark**. The MSSQL Spark connector supports two security modes to connect with SQL Server, non-Active Directory mode and Active Directory(AD)-mode:
+### Non-AD Mode:
+In non-AD mode security, each user has a username and password which need to be provided as parameters during the connector instantiation to perform read and/or writes.
+An example connector instantiation for non-AD mode is below:
+```python
+# Note: '?' is a placeholder for a necessary user-specified value
+connector_type = "com.microsoft.sqlserver.jdbc.spark" 
+
+url = "jdbc:sqlserver://master-p-svc;databaseName=?;"
+writer = df.write \ 
+   .format(connector_type)\ 
+   .mode("overwrite") 
+   .option("url", url) \ 
+   .option("user", ?) \ 
+   .option("password",?) 
+writer.save() 
+```
+### AD Mode:
+In AD mode security, after a user has generated a key tab file, the user needs to provide the `principal` and `keytab` as parameters during the connector instantiation.
+
+In this mode, the driver loads the keytab file to the respective executor containers. Then, the executors use the principal name and keytab to generate a token that is used to create a JDBC connector for read/write.
+
+An example connector instantiation for AD mode is below:
+```python
+# Note: '?' is a placeholder for a necessary user-specified value
+connector_type = "com.microsoft.sqlserver.jdbc.spark"
+
+url = "jdbc:sqlserver://master-p-svc;databaseName=?;integratedSecurity=true;authenticationScheme=JavaKerberos;" 
+writer = df.write \ 
+   .format(connector_type)\ 
+   .mode("overwrite") 
+   .option("url", url) \ 
+   .option("principal", ?) \ 
+   .option("keytab", ?)   
+
+writer.save() 
+```
 
 The following table describes interface parameters that have changed or are new:
 
@@ -40,13 +69,19 @@ The following table describes interface parameters that have changed or are new:
 
 The connector uses SQL Server Bulk write APIs. Any bulk write parameters can be passed as optional parameters by the user and are passed as-is by the connector to the underlying API. For more information about bulk write operations, see [SQLServerBulkCopyOptions]( ../connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md#sqlserverbulkcopyoptions).
 
-## Prerequisites
+## MSSQL Spark Connector Sample
+The sample performs the following tasks:
+
+- Read a file from HDFS and do some basic processing.
+- Write the dataframe to a SQL Server master instance as a SQL table and then read the table to a dataframe.
+- Write the dataframe to a SQL Server data pool as a SQL external table and then read the external table to a dataframe.
+### Prerequisites
 
 - A [SQL Server big data cluster](deploy-get-started.md).
 
 - [Azure Data Studio](https://aka.ms/getazuredatastudio).
 
-## Create the target database
+### Create the target database
 
 1. Open Azure Data Studio, and [connect to the SQL Server master instance of your big data cluster](connect-to-big-data-cluster.md).
 
@@ -57,7 +92,7 @@ The connector uses SQL Server Bulk write APIs. Any bulk write parameters can be
    GO
    ```
 
-## Load sample data into HDFS
+### Load sample data into HDFS
 
 1. Download [AdultCensusIncome.csv](https://amldockerdatasets.azureedge.net/AdultCensusIncome.csv) to your local machine.
 
@@ -69,9 +104,9 @@ The connector uses SQL Server Bulk write APIs. Any bulk write parameters can be
 
    ![AdultCensusIncome CSV file](./media/spark-mssql-connector/spark_data.png)
 
-## Run the sample notebook
+### Run the sample notebook
 
-To demonstrate the use of the MSSQL Spark Connector with this data, you can download a sample notebook, open it in Azure Data Studio, and run each code block. For more information about working with notebooks, see [How to use notebooks in SQL Server](notebooks-guidance.md).
+To demonstrate the use of the MSSQL Spark Connector with this data in non-AD mode, you can download a sample notebook, open it in Azure Data Studio, and run each code block. For more information about working with notebooks, see [How to use notebooks in SQL Server](notebooks-guidance.md).
 
 1. From a PowerShell or bash command line, run the following command to download the **mssql_spark_connector_non_ad_pyspark.ipynb** sample notebook:
 
@@ -86,3 +121,5 @@ To demonstrate the use of the MSSQL Spark Connector with this data, you can down
 ## Next steps
 
 For more information about big data clusters, see [How to deploy [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)] on Kubernetes](deployment-guidance.md)
+
+Have feedback or feature recommendations for SQL Server Big Data Clusters? [Leave us a note at SQL Server Big Data Clusters Feedback](https://aka.ms/sql-server-bdc-feedback).
diff --git a/docs/includes/media/yes.png b/docs/includes/media/yes.png
diff --git a/docs/linux/quickstart-install-connect-suse.md b/docs/linux/quickstart-install-connect-suse.md
@@ -25,7 +25,7 @@ In this quickstart, you install SQL Server 2017 or SQL Server 2019 on SUSE Linux
 In this quickstart, you install SQL Server 2019 on SUSE Linux Enterprise Server (SLES) v12. You then connect with **sqlcmd** to create your first database and run queries.
 
 > [!IMPORTANT]
-> SQL Server 2019 is supported on SUSE Enterprise Linux Server v12 SP2, SP3, or SP4.
+> SQL Server 2019 is supported on SUSE Enterprise Linux Server v12 SP2, SP3, SP4 or SP5.
 
 ::: moniker-end
 
@@ -44,7 +44,7 @@ You must have a SLES v12 SP2 machine with **at least 2 GB** of memory. The file
 <!--SQL Server 2019 on Linux-->
 ::: moniker range=">= sql-server-linux-ver15 || >= sql-server-ver15 || =sqlallproducts-allversions"
 
-You must have a SLES v12 SP2, SP3, or SP4 machine with **at least 2 GB** of memory. The file system must be **XFS** or **EXT4**. Other file systems, such as **BTRFS**, are unsupported.
+You must have a SLES v12 SP2, SP3, SP4 or SP5 machine with **at least 2 GB** of memory. The file system must be **XFS** or **EXT4**. Other file systems, such as **BTRFS**, are unsupported.
 
 ::: moniker-end
 
diff --git a/docs/linux/sample-unattended-install-ubuntu.md b/docs/linux/sample-unattended-install-ubuntu.md
@@ -26,6 +26,9 @@ This sample Bash script installs SQL Server 2017 on Ubuntu 16.04 without interac
 
 ## Sample script
 
+> [!NOTE]
+> The script might fail if SQL Server is slow to start. That's because the script will exit with a non-zero status. Removing the `-e` switch on the first line may resolve this issue.
+
 ```bash
 #!/bin/bash -e
 
diff --git a/docs/relational-databases/extended-events/quick-start-extended-events-in-sql-server.md b/docs/relational-databases/extended-events/quick-start-extended-events-in-sql-server.md
@@ -1,5 +1,6 @@
 ---
 title: "Quickstart: Extended events in SQL Server"
+description: This quickstart helps you use Extended Events, a lightweight performance monitoring system, to collect data to monitor and troubleshoot problems in SQL Server.
 ms.date: "05/28/2019"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/selects-and-joins-from-system-views-for-extended-events-in-sql-server.md b/docs/relational-databases/extended-events/selects-and-joins-from-system-views-for-extended-events-in-sql-server.md
@@ -1,5 +1,6 @@
 ---
 title: "SELECTs and JOINs from system views for extended events"
+description: There are system views of extended events in SQL Server and Azure SQL Database. Learn how event session information is represented in different perspectives.
 ms.date: "08/02/2016"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/sql-server-extended-events-engine.md b/docs/relational-databases/extended-events/sql-server-extended-events-engine.md
@@ -1,5 +1,6 @@
 ---
 title: "SQL Server Extended Events Engine"
+description: The SQL Server Extended Events engine enables the definition of events and processing of event data, manages Extended Events, and maintains a list of sessions.
 ms.date: "03/14/2017"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/sql-server-extended-events-packages.md b/docs/relational-databases/extended-events/sql-server-extended-events-packages.md
@@ -1,5 +1,6 @@
 ---
 title: "SQL Server Extended Events Packages"
+description: A package is a container for SQL Server Extended Events objects. This article describes the objects a package can contain.
 ms.date: "03/14/2017"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/sql-server-extended-events-sessions.md b/docs/relational-databases/extended-events/sql-server-extended-events-sessions.md
@@ -1,5 +1,6 @@
 ---
 title: "SQL Server Extended Events Sessions"
+description: A SQL Server Extended Events session is created in the SQL Server process that hosts the Extended Events engine. Learn about session states and session content.
 ms.date: "03/14/2017"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/targets-for-extended-events-in-sql-server.md b/docs/relational-databases/extended-events/targets-for-extended-events-in-sql-server.md
@@ -1,5 +1,6 @@
 ---
 title: "Targets for Extended Events in SQL Server"
+description: This article explains package0 targets for extended events in SQL Server. Learn about target abilities in gathering and reporting data and target parameters.
 ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/use-the-powershell-provider-for-extended-events.md b/docs/relational-databases/extended-events/use-the-powershell-provider-for-extended-events.md
@@ -1,5 +1,6 @@
 ---
 title: "Use the PowerShell Provider for Extended Events"
+description: Use the SQL Server PowerShell provider to manage SQL Server Extended Events. This article shows examples of creating, altering, and managing sessions.
 ms.date: "03/14/2017"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/use-the-ssms-xe-profiler.md b/docs/relational-databases/extended-events/use-the-ssms-xe-profiler.md
@@ -1,5 +1,6 @@
 ---
 title: "Use the SSMS XEvent Profiler"
+description: The XEvent Profiler displays a live viewer of extended events. Learn why to use this profiler, key features, and how to get started viewing extended events.
 ms.date: 10/02/2016
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
@@ -14,11 +15,11 @@ helpviewer_keywords:
 ms.assetid: 1e1fad43-d747-4775-ac0d-c50648e56d78
 author: "yualan"
 ms.author: "alayu"
-monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: ">=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017"
 ---
 # Use the SSMS XEvent Profiler
 
-[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
 The XEvent Profiler is a SQL Server Management Studio (SSMS) feature that displays a live viewer window of extended events. This overview describes the reasons for using this profiler, key features, and instructions to get started viewing extended events.
 
 ## Why would I use the XEvent Profiler?
diff --git a/docs/relational-databases/extended-events/use-the-system-health-session.md b/docs/relational-databases/extended-events/use-the-system-health-session.md
@@ -1,5 +1,6 @@
 ---
 title: "Use the system_health Session"
+description: The system_health Extended Events session is included with SQL Server. This session collects system data to troubleshoot performance for the Database Engine.
 ms.date: "11/27/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/view-the-extended-events-equivalents-to-sql-trace-event-classes.md b/docs/relational-databases/extended-events/view-the-extended-events-equivalents-to-sql-trace-event-classes.md
@@ -1,5 +1,6 @@
 ---
 title: "Extended events equivalents to SQL Trace Event classes"
+description: This article shows you how to view the Extended Events actions and events that are equivalent to each SQL Trace event and its associated columns.
 ms.date: "03/05/2017"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/extended-events/xevents-references-system-objects.md b/docs/relational-databases/extended-events/xevents-references-system-objects.md
@@ -1,5 +1,6 @@
 ---
 title: "XEvents related system objects"
+description: These resources relate to extended events, including how system objects support them, how SQL Server uses them, and aspects particular to Azure SQL Database.
 ms.date: 03/24/2019
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
diff --git a/docs/relational-databases/indexes/reorganize-and-rebuild-indexes.md b/docs/relational-databases/indexes/reorganize-and-rebuild-indexes.md
@@ -2,7 +2,7 @@
 title: "Reorganize and Rebuild Indexes | Microsoft Docs"
 description:: This article describes why index fragmentation is a bad thing and how to fix it using T-SQL and SQL Server Management Studio.
 ms.custom: ""
-ms.date: "03/10/2020"
+ms.date: "03/18/2020"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
 ms.reviewer: carlrab
@@ -37,7 +37,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 [!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
 
-This article describes how to reorganize or rebuild a fragmented index in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)].
+This article discusses what index defragmentation is and why it affects performance. This article also explains the difference between reorganizing an index vs. rebuilding an index. Finally, it describes how to reorganize or rebuild a fragmented index in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)].
 
 ## Index fragmentation overview
 
@@ -218,7 +218,7 @@ Requires `ALTER` permission on the table or view. User must be a member of at le
 > [!NOTE]
 > [!INCLUDE[ssManStudio](../../includes/ssManStudio-md.md)] cannot be used to compute fragmentation of columnstore indexes in SQL Server and cannot be used to compute fragmentation of any indexes in Azure SQL Database. Use the folowing [!INCLUDE[tsql](../../includes/tsql-md.md)] [example](#TsqlProcedureFrag).
 
-1. In Object Explorer, Expand the database that contains the table on which you want to check an index's fragmentation.
+1. In Object Explorer, expand the database that contains the table on which you want to check an index's fragmentation.
 2. Expand the **Tables** folder.
 3. Expand the table on which you want to check an index's fragmentation.
 4. Expand the **Indexes** folder.
diff --git a/docs/relational-databases/sql-server-index-design-guide.md b/docs/relational-databases/sql-server-index-design-guide.md
@@ -202,7 +202,7 @@ ON Purchasing.PurchaseOrderDetail
   
  The [!INCLUDE[ssDE](../includes/ssde-md.md)] can move equally efficiently in either direction. An index defined as `(RejectedQty DESC, ProductID ASC)` can still be used for a query in which the sort direction of the columns in the ORDER BY clause are reversed. For example, a query with the ORDER BY clause `ORDER BY RejectedQty ASC, ProductID DESC` can use the index.  
   
- Sort order can be specified only for key columns. The [sys.index_columns](../relational-databases/system-catalog-views/sys-index-columns-transact-sql.md) catalog view and the INDEXKEY_PROPERTY function report whether an index column is stored in ascending or descending order.  
+ Sort order can be specified only for the key columns in index. The [sys.index_columns](../relational-databases/system-catalog-views/sys-index-columns-transact-sql.md) catalog view and the INDEXKEY_PROPERTY function report whether an index column is stored in ascending or descending order.  
 
 ## Metadata  
 Use these metadata views to see attributes of indexes. More architectural information is embedded in some of these views.
diff --git a/docs/relational-databases/user-defined-functions/scalar-udf-inlining.md b/docs/relational-databases/user-defined-functions/scalar-udf-inlining.md
diff --git a/docs/reporting-services/reporting-services-tutorials-ssrs.md b/docs/reporting-services/reporting-services-tutorials-ssrs.md
diff --git a/docs/reporting-services/tools/tutorial-how-to-locate-and-start-reporting-services-tools-ssrs.md b/docs/reporting-services/tools/tutorial-how-to-locate-and-start-reporting-services-tools-ssrs.md
diff --git a/docs/t-sql/functions/ranking-functions-transact-sql.md b/docs/t-sql/functions/ranking-functions-transact-sql.md
diff --git a/docs/t-sql/functions/suser-sid-transact-sql.md b/docs/t-sql/functions/suser-sid-transact-sql.md
diff --git a/docs/t-sql/statements/restore-statements-headeronly-transact-sql.md b/docs/t-sql/statements/restore-statements-headeronly-transact-sql.md
