Merge pull request #19939 from NathanMSFT/20210805_limitations

20210805 1613 - documenting limitations/requirements

Author: Court72

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

@@ -1,7 +1,7 @@
 ---
 title: "Configure PolyBase scale-out groups on Windows"
 description: Set up a PolyBase scale-out group to create a cluster of SQL Server instances. This improves query performance for large data sets from external sources.
-ms.date: 07/07/2021
+ms.date: 08/05/2021
 ms.prod: sql
 ms.technology: polybase
 ms.topic: "tutorial"
@@ -100,7 +100,10 @@ After setup is complete, both machines can function as PolyBase Group head nodes
 4. Start PolyBase Engine. Restart PolyBase data movement service.
 
 5. Verify that the node has been removed by running the DMV sys.dm_exec_compute_nodes on PQTH4A-CMP01. Now, PQTH4A-CMP02 will function as a standalone head node  
-  
+
+## Known limitations
+If you have a default SQL Server instance that is configured to listen on TCP port other than 1433, you cannot use it as a head node in a PolyBase scale-out group. When executing `sp_polybase_join_group`, if you pass 'MSSQLSERVER' as the instance name, SQL Server will assume port 1433 is the listener port, so the Data Movement service will be unable to connect to the head node when starting.
+
 ## Next steps  
 
 For troubleshooting, see [PolyBase troubleshooting with dynamic management views](/previous-versions/sql/sql-server-2016/mt146389(v=sql.130)).

docs/relational-databases/polybase/polybase-faq.yml

@@ -2,7 +2,7 @@
 metadata:
   title: "Frequently Asked Questions in PolyBase"
   description: Compare PolyBase and linked servers and compare PolyBase in Big Data Clusters and PolyBase in stand-alone instances. Find out what's new in PolyBase 2019.
-  ms.date: 07/07/2021
+  ms.date: 08/13/2021
   ms.prod: sql
   ms.technology: polybase
   ms.topic: conceptual
@@ -88,7 +88,7 @@ sections:
           | Source platform | Reference | 
           | ---- | ---- |
           | Microsoft SQL Server | [Ports Used By SQL Server](../../sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access.md#ports-used-by-)| 
-          | Hadoop HDFS | [Administering HDFS](https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/administration/content/hdfs-ports.html)|
+          | Hortonworks HDP | [Administering HDFS](https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/administration/content/hdfs-ports.html)|
           | Cloudera CDH | [Ports Used by CDH Components](https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cdh_ports.html)| 
           | | | 
 

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

@@ -1,7 +1,7 @@
 ---
 title: "Install PolyBase on Windows"
 description: Learn to install PolyBase as a single node or PolyBase scale-out group. You can use an installation wizard or a command prompt. Finally, enable PolyBase.
-ms.date: 06/09/2021
+ms.date: 08/05/2021
 ms.prod: sql
 ms.technology: polybase
 ms.topic: conceptual
@@ -32,6 +32,8 @@ To install a trial version of SQL Server, go to [SQL Server evaluations](https:/
 
 - PolyBase services require SQL Server service to have TCP/IP network protocol enabled to function correctly. TCP/IP is enabled by default on all editions of SQL Server except for the Developer and Express SQL Server editions. For PolyBase to function correctly on the Developer and Express editions, you must enable TCP/IP connectivity. See [Enable or disable a server network protocol](../../database-engine/configure-windows/enable-or-disable-a-server-network-protocol.md). Additionally, if TCP/IP Protocol configuration setting **Listen All** is set to **No**, you must still have an entry for the correct listener port in either **TCP Dynamic Ports** or **TCP Ports** under **IPAll** in TCP/IP Properties. This is required due to the way PolyBase services resolve the listener port of the SQL Server Engine.
 
+- PolyBase services require Shared Memory protocol to be enabled to function properly.
+
 >[!NOTE] 
 > PolyBase can be installed on only one SQL Server instance per machine.
 

docs/relational-databases/polybase/polybase-versioned-feature-summary.md

@@ -2,7 +2,7 @@
 description: "PolyBase features and limitations"
 title: "PolyBase features and limitations"
 descriptions: This article summarizes PolyBase features available for SQL Server products and services. It lists T-SQL operators supported for pushdown and known limitations.
-ms.date: 04/19/2021
+ms.date: 08/05/2021
 ms.prod: sql
 ms.technology: polybase
 ms.topic: conceptual
@@ -54,6 +54,10 @@ PolyBase has the following limitations:
 
 - PolyBase on SQL Server on Linux will not function if IPv6 is disabled in the kernel. See [Release notes for SQL Server 2019 on Linux](../../linux/sql-server-linux-release-notes-2019.md#networking) for further information on this limitation.
 
+- PolyBase services require Shared Memory protocol to be enabled to function properly.
+
+- If you have a default SQL Server instance that is configured to listen on TCP port other than 1433, you cannot use it as a head node in a PolyBase scale-out group. When executing sp_polybase_join_group, if you pass 'MSSQLSERVER' as the instance name, SQL Server will assume port 1433 is the listener port, so the Data Movement service will be unable to connect to the head node when starting.
+
 <!--SQL Server 2016-->
 ::: moniker range="= sql-server-2016 "