Adds missing PolyBase parameters

Also correct capitalization of feature

Author: rwestMSFT

docs/database-engine/install-windows/install-sql-server-database-engine.md

@@ -53,7 +53,7 @@ The following features are installed when you select **[!INCLUDE[ssNoVersion](..
     > [!NOTE]  
     >  In this release, selecting the **Data Quality Services** check box in setup does not install the Data Quality Services (DQS) server. You will have to perform additional steps post installation to install DQS server. For more information, see [Install Data Quality Services](../../data-quality-services/install-windows/install-data-quality-services.md).  
     
-- [Polybase Query Service for External Data](../../relational-databases/polybase/polybase-guide.md) - is an optional component. Starting with SQL Server 2019, Java connector for HDFS data sources is also available.
+- [PolyBase Query Service for External Data](../../relational-databases/polybase/polybase-guide.md) - is an optional component. Starting with SQL Server 2019, Java connector for HDFS data sources is also available.
 
 
  The following additional features are options for many typical user scenarios:  

docs/database-engine/install-windows/install-sql-server-from-the-command-prompt.md

@@ -187,9 +187,12 @@ Use the parameters in the following table to develop command-line scripts for in
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Setup Control|/INSTANCEDIR<br /><br /> **Optional**|Specifies a nondefault installation directory for instance-specific components.|
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Setup Control|/INSTANCEID<br /><br /> **Optional**|Specifies a nondefault value for an [InstanceID](#InstanceID).|
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Setup Control|/INSTANCENAME<br /><br /> **Required**|Specifies a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance name.<br /><br /> For more information, see [Instance Configuration](../../sql-server/install/instance-configuration.md).|
-|PolyBase|/PBENGSVCACCOUNT<br /><br /> **Optional**|Specifies the account for the engine service. The default is **NT Authority\NETWORK SERVICE**.|
-|PolyBase|/PBDMSSVCPASSWORD<br /><br /> **Optional**|Specifies the password for the engine service account. This parameter can be omitted when using a managed service account, virtual account, or built-in account.|
-|PolyBase|/PBENGSVCSTARTUPTYPE<br /><br /> **Optional**|Specifies the startup mode for the PolyBase engine service: Automatic (default), Disabled,  and Manual.|
+|PolyBase Engine|/PBENGSVCACCOUNT<br /><br /> **Optional**|Specifies the account for the engine service. The default is **NT Authority\NETWORK SERVICE**.|  
+|PolyBase Engine|/PBENGSVCPASSWORD<br /><br /> **Optional**|Specifies the password for the engine service account.|  
+|PolyBase Engine|/PBENGSVCSTARTUPTYPE<br /><br /> **Optional**|Specifies the startup mode for the PolyBase Engine: Automatic (default), Disabled, and Manual.|  
+|PolyBase Data Movement |/PBDMSSVCACCOUNT<br /><br /> **Optional**|Specifies the account for the data movement service. The default is **NT Authority\NETWORK SERVICE**.|  
+|PolyBase Data Movement |/PBDMSSVCPASSWORD<br /><br /> **Optional**|Specifies the password for the data movement account.|  
+|SQL Server PolyBase Data Movement |/PBDMSSVCSTARTUPTYPE<br /><br /> **Optional**|Specifies the startup mode for the data movement service: Automatic (default), Disabled, and Manual.|  
 |PolyBase|/PBPORTRANGE<br /><br /> **Optional**|Specifies a port range with at least 6 ports for PolyBase services. Example:<br /><br /> `/PBPORTRANGE=16450-16460`|
 |PolyBase|/PBSCALEOUT<br /><br /> **Optional**|Specifies if the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] instance will be used as a part of PolyBase Scale-out computational group. Use this option if you are configuring a PolyBase Scale-out computational group including the head node. Supported values: **True**, **False**|
 |[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Setup Control|/PID<br /><br /> **Optional**|Specifies the product key for the edition of SQL Server. If this parameter is not specified, Evaluation is used.|
@@ -903,7 +906,7 @@ To install specific features, use the /FEATURES parameter and specify the parent
 ||FullText|Installs the FullText component along with [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)].|
 ||DQ|Copies the files required for completing the [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] installation. After completing SQL Server installation, you must run the DQSInstaller.exe file to complete the [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] installation. For more information, see [Run DQSInstaller.exe to Complete Data Quality Server Installation](../../data-quality-services/install-windows/run-dqsinstaller-exe-to-complete-data-quality-server-installation.md). This also installs [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)].|
 ||PolyBase |Installs PolyBase components.|
-||PolyBaseCore | Starting with SQL Server 2019, pair with **PolyBase** to install Polybase technology that enables truly integrated querying across Oracle, Teradata, SQL Server and other relational and non-relational data using standard T-SQL statements. |
+||PolyBaseCore | Starting with SQL Server 2019, pair with **PolyBase** to install PolyBase technology that enables truly integrated querying across Oracle, Teradata, SQL Server and other relational and non-relational data using standard T-SQL statements. |
 || PolyBaseJava | Starting with SQL Server 2019, pair with **PolyBase** to install PolyBase Java Connector that enables truly integrated querying across HDFS data using standard T-SQL statements.
 ||AdvancedAnalytics |Installs [SQL Server Machine Learning Services](../../machine-learning/install/sql-machine-learning-services-windows-install.md) or [SQL Server 2016 R Services (In-Database)](../../machine-learning/install/sql-r-services-windows-install.md).|
 ||SQL_INST_MR |Applies to [SQL Server Machine Learning Services](../../machine-learning/install/sql-machine-learning-services-windows-install.md) (2017 or later) and [SQL Server 2016 R Services (In-Database)](../../machine-learning/install/sql-r-services-windows-install.md). Pair with **AdvancedAnalytics** to install R Open and proprietary R packages.|

docs/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup.md

@@ -163,7 +163,7 @@ This is not applicable to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.m
 
      The workflow for the rest of the installation depends on the features that you've specified for your installation. Depending on your selections, you might not see all the pages. 
 
-1. Selecting to install the Polybase feature will add the **PolyBase Configuration** page to the SQL Server setup, displayed after the **Instance Configuration** page. PolyBase requires the Oracle JRE 7 Update 51 (at least), and if this hasn't already been installed, your installation will be blocked. On the **Polybase Configuration** page, you can choose to use the SQL Server as a standalone Polybase-enabled instance, or you can use this SQL Server as part of a PolyBase scale-out group. If you choose to use the scale-out group, you will need to specify a port range of up to 6 or more ports. 
+1. Selecting to install the PolyBase feature will add the **PolyBase Configuration** page to the SQL Server setup, displayed after the **Instance Configuration** page. PolyBase requires the Oracle JRE 7 Update 51 (at least), and if this hasn't already been installed, your installation will be blocked. On the **PolyBase Configuration** page, you can choose to use the SQL Server as a standalone PolyBase-enabled instance, or you can use this SQL Server as part of a PolyBase scale-out group. If you choose to use the scale-out group, you will need to specify a port range of up to 6 or more ports. 
 
 
 1. Use the **Server Configuration - Service Accounts** page to specify the logon accounts for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] services. The actual services that you configure on this page depend on the features that you selected to install. For more information about configuration settings, see [Installation Wizard help](../../sql-server/install/instance-configuration.md#serverconfig).
@@ -332,7 +332,7 @@ This is not applicable to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.m
 
      The workflow for the rest of the installation depends on the features that you've specified for your installation. Depending on your selections, you might not see all the pages. 
 
-1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], Polybase no longer requires that Oracle JRE 7 Update 51 (at least) be pre-installed on the computer prior to installing the feature. Selecting to install the Polybase feature will add the **Java Install Location** page to the SQL Server setup displayed after the **Instance Configuration** page. On the Java Install Location page, you can choose to install the Azul Zulu Open JRE included with the [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
+1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], PolyBase no longer requires that Oracle JRE 7 Update 51 (at least) be pre-installed on the computer prior to installing the feature. Selecting to install the PolyBase feature will add the **Java Install Location** page to the SQL Server setup displayed after the **Instance Configuration** page. On the Java Install Location page, you can choose to install the Azul Zulu Open JRE included with the [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
 
 1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], Java has been added with Language Extensions. Selecting to install the Java feature will add the **Java Install Location** page to the SQL Server setup dialog window, displayed after the **Instance Configuration** page. On the **Java Install Location** page, you can choose to install the Zulu Open JRE included with the [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
 
@@ -525,7 +525,7 @@ This is not applicable to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.m
 
      The workflow for the rest of the installation depends on the features that you've specified for your installation. Depending on your selections, you might not see all the pages. 
 
-1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], Polybase no longer requires that Oracle JRE 7 Update 51 (at least) be pre-installed on the computer prior to installing the feature. Selecting to install the Polybase feature will add the **Java Install Location** page to the SQL Server setup displayed after the **Instance Configuration** page. On the Java Install Location page, you can choose to install the Azul Zulu Open JRE included with the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
+1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], PolyBase no longer requires that Oracle JRE 7 Update 51 (at least) be pre-installed on the computer prior to installing the feature. Selecting to install the PolyBase feature will add the **Java Install Location** page to the SQL Server setup displayed after the **Instance Configuration** page. On the Java Install Location page, you can choose to install the Azul Zulu Open JRE included with the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
 
 1. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], Java has been added with Language Extensions. Selecting to install the Java feature will add the **Java Install Location** page to the SQL Server setup dialog window, displayed after the **Instance Configuration** page. On the **Java Install Location** page, you can choose to install the Zulu Open JRE included with the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
 

docs/index.yml

@@ -188,7 +188,7 @@ additionalContent:
             url: machine-learning/index.yml
           - text: SQL Server Big Data Clusters
             url: ./big-data-cluster/big-data-cluster-overview.md
-          - text: Data Virtualization with Polybase
+          - text: Data Virtualization with PolyBase
             url: relational-databases/polybase/polybase-guide.md
           - text: Microsoft Analytics Platform System
             url: ./analytics-platform-system/home-analytics-platform-system-aps-pdw.md

docs/linux/sql-server-linux-docker-container-configure.md

@@ -464,7 +464,7 @@ For examples of custom Docker containers, see <https://github.com/microsoft/mssq
 - [Dockerfile example with Full-Text Search](https://github.com/microsoft/mssql-docker/blob/master/linux/preview/examples/mssql-agent-fts-ha-tools/Dockerfile)
 - [Dockerfile example for RHEL 7 and SQL Server 2019](https://github.com/microsoft/mssql-docker/tree/master/linux/preview/examples/mssql-rhel7-sql2019)
 - [Dockerfile example for RHEL 8 and SQL Server 2017](https://github.com/microsoft/mssql-docker/tree/master/linux/preview/examples/mssql-rhel8-sql2017)
-- [Dockerfile example for Ubuntu 20.04 and SQL Server 2019 with Full-Text Search, Polybase, and Tools](https://github.com/microsoft/mssql-docker/blob/master/linux/preview/examples/mssql-polybase-fts-tools/Dockerfile)
+- [Dockerfile example for Ubuntu 20.04 and SQL Server 2019 with Full-Text Search, PolyBase, and Tools](https://github.com/microsoft/mssql-docker/blob/master/linux/preview/examples/mssql-polybase-fts-tools/Dockerfile)
 
 For information on how to build and run Docker containers using Dockerfiles, see <https://github.com/microsoft/mssql-docker/tree/master/linux/preview/examples/mssql-mlservices>.
 

docs/relational-databases/polybase/configure-scale-out-groups-windows.md

@@ -85,7 +85,7 @@ After setup is complete, both machines can function as PolyBase Group head nodes
 4. Shutdown the PolyBase engine and restart the PolyBase data movement service.
 
 > [!NOTE] 
-> When the Polybase Engine service gets restarted or stopped in the head node, the Data Movement Service (DMS) services gets stopped as soon as the communication channel is closed between DMS and Polybase Engine Service (DW). If the DW engine gets restarted more than two times, the DMS goes to a quiet period for 90 minutes and it must wait 90 minutes for the next auto start attempt. In such situation, you should start this service manually on all nodes.
+> When the PolyBase Engine service gets restarted or stopped in the head node, the Data Movement Service (DMS) services gets stopped as soon as the communication channel is closed between DMS and PolyBase Engine Service (DW). If the DW engine gets restarted more than two times, the DMS goes to a quiet period for 90 minutes and it must wait 90 minutes for the next auto start attempt. In such situation, you should start this service manually on all nodes.
 
 ## Optional: Remove a compute node  
 

docs/relational-databases/polybase/polybase-configure-hadoop.md

@@ -64,7 +64,7 @@ To improve query performance, enable pushdown computation to your Hadoop cluster
 1. Find the file **yarn-site.xml** in the installation path of SQL Server. Typically, the path is:  
 
    ```xml  
-   C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\Polybase\Hadoop\conf\  
+   C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\PolyBase\Hadoop\conf\  
    ```  
 
 1. On the Hadoop machine, find the analogous file in the Hadoop configuration directory. In the file, find and copy the value of the configuration key yarn.application.classpath.  

docs/relational-databases/polybase/polybase-errors-and-possible-solutions.md

@@ -102,7 +102,7 @@ Interrogation of DWEngine Server log shows the following error:
 Microsoft.SqlServer.DataWarehouse.Common.ErrorHandling.MppSqlException: EXTERNAL TABLE access failed due to internal error: 'Java exception raised on call to HdfsBridge_Connect: Error [com.microsoft.polybase.client.KerberosSecureLogin] occurred while accessing external file.' ---> Microsoft.SqlServer.DataWarehouse.DataMovement.Common.ExternalAccess.HdfsAccessException: Java exception raised on call to HdfsBridge_Connect: Error [com.microsoft.polybase.client.KerberosSecureLogin] occurred while accessing external file.
 
 **Possible Reason:**  
-Kerberos is not enabled in Hadoop Cluster, but Kerberos security is enabled in core-site.xml, yarn-site.xml, or the hdfs-site.xml located by default under Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\Polybase\Hadoop\conf. In Linux, the files are by default located in /var/opt/mssql/binn/polybase/hadoop/conf/.
+Kerberos is not enabled in Hadoop Cluster, but Kerberos security is enabled in core-site.xml, yarn-site.xml, or the hdfs-site.xml located by default under Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\PolyBase\Hadoop\conf. In Linux, the files are by default located in /var/opt/mssql/binn/polybase/hadoop/conf/.
 
 **Possible Solution:**  
 Comment out the Kerberos security information from the above mentioned files.

docs/relational-databases/polybase/polybase-troubleshooting.md

@@ -264,7 +264,7 @@ Use DNS name to reroute connections to the active Name Node. In order to do this
 
 ## Log file locations
 
-In Windows servers, the logs are located in the installation directory path, by default: c:\Program Files\Microsoft SQL Server\MSSQLnn.InstanceName\MSSQL\Log\Polybase\.
+In Windows servers, the logs are located in the installation directory path, by default: c:\Program Files\Microsoft SQL Server\MSSQLnn.InstanceName\MSSQL\Log\PolyBase\.
 
 In Linux servers, the logs are located by default in /var/opt/mssql/log/polybase.
 

docs/relational-databases/system-dynamic-management-views/sys-dm-os-memory-clerks-transact-sql.md

@@ -122,7 +122,7 @@ The following table lists the memory clerk types:
 |MEMORYCLERK_HOST     |    This memory clerk is used for allocations by SQL OS functionality.     |
 |MEMORYCLERK_LANGSVC     |     This memory clerk is used for allocations by SQL T-SQL statements and commands (parser, algebrizer, etc.)    |
 |MEMORYCLERK_LWC     |   This memory clerk is used for allocations by Full-Text [Semantic Search](../search/semantic-search-sql-server.md) engine       |
-|MEMORYCLERK_POLYBASE     |    This memory clerk keeps track of memory allocations for [Polybase](../polybase/polybase-guide.md) functionality inside SQL Server.     |
+|MEMORYCLERK_POLYBASE     |    This memory clerk keeps track of memory allocations for [PolyBase](../polybase/polybase-guide.md) functionality inside SQL Server.     |
 |MEMORYCLERK_QSRANGEPREFETCH     |  This memory clerk is used for allocations during query execution for query scan range prefetch.      |
 |MEMORYCLERK_QUERYDISKSTORE     |     This memory clerk is used by [Query Store](../performance/monitoring-performance-by-using-the-query-store.md) memory allocations inside SQL Server.    |
 |MEMORYCLERK_QUERYDISKSTORE_HASHMAP     |   This memory clerk is used by [Query Store](../performance/monitoring-performance-by-using-the-query-store.md) memory allocations inside SQL Server.      |