You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/relational-databases/polybase/configure-scale-out-groups-windows.md
+31-29Lines changed: 31 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Configure PolyBase scale-out groups on Windows"
3
3
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.
This article describes how to set up a [PolyBase scale-out group](polybase-scale-out-groups.md) on Windows. This creates a cluster of SQL Server instances to process large data sets from external data sources, such as Hadoop or Azure Blob Storage, in a scale-out fashion for better query performance.
@@ -29,13 +29,13 @@ The following steps summarize the process for creating a PolyBase scale-out grou
29
29
30
30
1. Install the same version of SQL Server with PolyBase on N machines.
31
31
32
-
2. Select one SQL Server instance as the head node.
32
+
1. Select one SQL Server instance as the head node.
33
33
34
-
3. Add remaining SQL Server instances as compute nodes using [sp_polybase_join_group](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-join-group.md).
34
+
1. Add remaining SQL Server instances as compute nodes using [sp_polybase_join_group](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-join-group.md).
35
35
36
-
4. Monitor nodes in the group using [sys.dm_exec_compute_nodes (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-compute-nodes-transact-sql.md).
36
+
1. Monitor nodes in the group using [sys.dm_exec_compute_nodes (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-compute-nodes-transact-sql.md).
37
37
38
-
5. Optional. Remove a compute node from using [sp_polybase_leave_group (Transact-SQL)](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-leave-group.md).
38
+
1. Optional. Remove a compute node from using [sp_polybase_leave_group (Transact-SQL)](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-leave-group.md).
39
39
40
40
## Example walk-through
41
41
@@ -47,66 +47,68 @@ This walks through the steps of configuring a PolyBase Group using:
47
47
48
48
- PQTH4A-CMP02
49
49
50
-
2. Domain account: *PQTH4A\PolyBaseUse*r
50
+
1. Domain account: *PQTH4A\PolyBaseUser*
51
51
52
52
## Install SQL Server with PolyBase on all machines
53
53
54
54
1. Run setup.exe.
55
55
56
-
2. On the Feature Selection page, select **PolyBase Query Service for External Data**.
56
+
1. On the Feature Selection page, select **PolyBase Query Service for External Data**.
57
57
58
-
3. On the Server Configuration page, use the **domain account** PQTH4A\PolyBaseUser for SQL Server PolyBase Engine and SQL Server PolyBase Data Movement Service.
58
+
1. On the Server Configuration page, use the **domain account** PQTH4A\PolyBaseUser for SQL Server PolyBase Engine and SQL Server PolyBase Data Movement Service.
59
59
60
-
4. On the PolyBase Configuration page, select the option **Use the SQL Server instance as part of a PolyBase scale-out group**. This opens the firewall to allow incoming connections to the PolyBase services. SQL Server installation wizard automatically exposes the following TCP ports in the Windows Server Firewall: 1433,16450-16453, and 17001. If the head node is a SQL Server named instance, you must also manually add the SQL Server port to the Windows firewall on the head node and also start the SQL Browser on the head node. Ports should be allowed only on the firewalls of servers in the PolyBase scale-out group.
60
+
1. On the PolyBase Configuration page, select the option **Use the SQL Server instance as part of a PolyBase scale-out group**. This opens the firewall to allow incoming connections to the PolyBase services. SQL Server installation wizard automatically exposes the following TCP ports in the Windows Server Firewall: 1433,16450-16453, and 17001. If the head node is a SQL Server named instance, you must also manually add the SQL Server port to the Windows Firewall on the head node and also start the SQL Browser on the head node. Ports should be allowed only on the firewalls of servers in the PolyBase scale-out group.
61
61
62
-
5. After setup is complete, run **services.msc**. Verify that SQL Server, PolyBase Engine and PolyBase Data Movement Service are running.
62
+
1. After setup is complete, run **services.msc**. Verify that SQL Server, PolyBase Engine and PolyBase Data Movement Service are running.
:::image type="content" source="media/configure-scale-out-groups-windows/polybase-services.png" alt-text="A screenshot from SQL Server Configuration Manager, showing the PolyBase services.":::
65
65
66
-
## Select one SQL Server as head node
66
+
## Select one SQL Server as head node
67
67
68
-
After setup is complete, both machines can function as PolyBase Group head nodes. In this example, we will choose "MSSQLSERVER" on PQTH4A-CMP01 as the head node.
68
+
After setup is complete, both machines can function as PolyBase Group head nodes. In this example, we choose the "MSSQLSERVER" instance on PQTH4A-CMP01 as the head node.
69
69
70
-
## Add other SQL Server instances as compute nodes
70
+
## Add other SQL Server instances as compute nodes
71
71
72
72
1. Connect to SQL Server on PQTH4A-CMP02.
73
73
74
-
2. Run the stored procedure [sp_polybase_join_group](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-join-group.md).
74
+
1. Run the stored procedure [sp_polybase_join_group](../../relational-databases/system-stored-procedures/polybase-stored-procedures-sp-polybase-join-group.md).
75
75
76
76
```sql
77
77
-- Enter head node details:
78
78
-- head node machine name, head node dms control channel port, head node sql server name
3. Run services.msc on the compute node (PQTH4A-CMP02).
82
+
1. Run services.msc on the compute node (PQTH4A-CMP02).
83
83
84
-
4. Shutdown the PolyBase engine and restart the PolyBase data movement service.
84
+
1. Shut down the PolyBase engine and restart the PolyBase data movement service.
85
85
86
86
> [!NOTE]
87
87
> 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.
88
88
89
-
## Optional: Remove a compute node
89
+
## Optional: Remove a compute node
90
90
91
91
1. Connect to the compute node SQL Server (PQTH4A-CMP02).
92
92
93
-
2. Run the stored procedure sp_polybase_leave_group.
93
+
1. Run the stored procedure `sp_polybase_leave_group`.
94
94
95
95
```sql
96
96
EXEC sp_polybase_leave_group;
97
97
```
98
98
99
-
3. Run services.mscon the compute node that is being removed (PQTH4A-CMP02).
99
+
1. Run services.mscon the compute node that is being removed (PQTH4A-CMP02).
100
100
101
-
4. Start PolyBase Engine. Restart PolyBase data movement service.
101
+
1. Start PolyBase Engine. Restart PolyBase data movement service.
102
102
103
-
5. Verify that the node has been removed by running the DMV sys.dm_exec_compute_nodeson PQTH4A-CMP01. Now, PQTH4A-CMP02 will function as a standalone head node
103
+
1. 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
104
104
105
-
## Known limitations
106
-
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.
105
+
## Limitations
107
106
108
-
## Next steps
107
+
- 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 assumes port 1433 is the listener port, so the Data Movement service is unable to connect to the head node when starting.
109
108
110
-
For troubleshooting, see [PolyBase troubleshooting with dynamic management views](/previous-versions/sql/sql-server-2016/mt146389(v=sql.130)).
111
-
112
-
For more information about PolyBase, see the [PolyBase overview](../../relational-databases/polybase/polybase-guide.md).
109
+
- PolyBase scale-out groups are not supported with Always On availability groups.
110
+
111
+
## Related content
112
+
113
+
- [PolyBase troubleshooting with dynamic management views](/previous-versions/sql/sql-server-2016/mt146389(v=sql.130))
114
+
- [Introducing data virtualization with PolyBase](polybase-guide.md)
0 commit comments