20210707 latest from David Kryze

Author: WilliamDAssafMSFT

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

@@ -1,13 +1,13 @@
 ---
 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: 06/09/2021
+ms.date: 07/07/2021
 ms.prod: sql
 ms.technology: polybase
 ms.topic: "tutorial"
-author: MikeRayMSFT
-ms.author: mikeray
-ms.reviewer: ""
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: 
 monikerRange: ">= sql-server-2016"
 ---
 # Configure PolyBase scale-out groups on Windows

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

@@ -2,12 +2,12 @@
 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: 6/09/2021
+  ms.date: 07/07/2021
   ms.prod: sql
   ms.technology: polybase
   ms.topic: conceptual
-  author: MikeRayMSFT
-  ms.author: mikeray
+  author: WilliamDAssafMSFT
+  ms.author: wiassaf
   ms.reviewer: mikeray
   monikerRange: ">= sql-server-linux-ver15 || >= sql-server-2016"
 
@@ -75,14 +75,13 @@ sections:
         answer: |
           See [How to tell if external pushdown occurred](polybase-how-to-tell-pushdown-computation.md).
 
-      - question: What ports are used by default for PolyBase scale-out group? 
-        answer: | 
-          By default, the PolyBase data movement service connects to the head node of a scale-out group over a range of ports from TCP 16450-16460, typically using 16450-16453, plus port 17001. These ports are only used when a PolyBase scale-out group is configured and should be allowed through server firewalls.          
-          SQL Server Setup should automatically create a local firewall rule allowing these ports upon feature installation.
-          
       - question: Which ports should I allow through my firewall for PolyBase?
         answer: | 
-          No additional ports are needed to open for PolyBase itself, except in the case of a PolyBase scale-out group. However, you must allow other ports based on the external data source(s) in use. Refer to specific external data source documentation. For example:
+          No additional ports are needed to open for PolyBase itself, except in the case of a PolyBase scale-out group. Without a scale-out group, the PolyBase service alone should not require any firewall rule. PolyBase will leverage the ports used by SQL Server in the **IPAll** section of the TCP/IP settings in SQL Server Configuration Manager. For more information, see [TCP/IP Properties](/sql/tools/configuration-manager/tcp-ip-properties-ip-addresses-tab).
+          
+          For PolyBase scale-out groups over multiple Windows servers, see port information in the next question.
+
+          However, you must allow other ports for communication to the various external data source(s) used by PolyBase. Refer to specific external data source documentation, which may be an external vendor. For example:
 
           | Source platform | Reference | 
           | ---- | ---- |
@@ -91,7 +90,10 @@ sections:
           | Cloudera CDH | [Ports Used by CDH Components](https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cdh_ports.html)| 
           | | | 
 
-
+      - question: What ports are used for PolyBase scale-out group? 
+        answer: | 
+          By default, the PolyBase data movement service connects to the head node of a scale-out group over a range of ports from TCP 16450-16460, typically using 16450-16453, plus port 17001. These ports are only used when a PolyBase scale-out group is configured and should be allowed through server firewalls. SQL Server Setup should automatically create a local firewall rule allowing these ports upon feature installation. For more information, see [Configure PolyBase scale-out groups on Windows](configure-scale-out-groups-windows.md). 
+