| title | sp_polybase_leave_group (Transact-SQL) | ||
|---|---|---|---|
| description | Removes a SQL Server instance from a PolyBase group for scale-out computation. | ||
| author | markingmyname | ||
| ms.author | maghan | ||
| ms.reviewer | randolphwest | ||
| ms.date | 06/23/2025 | ||
| ms.service | sql | ||
| ms.subservice | polybase | ||
| ms.topic | reference | ||
| f1_keywords |
|
||
| helpviewer_keywords |
|
||
| dev_langs |
|
[!INCLUDE sqlserver2016]
Removes a SQL Server instance from a PolyBase group for scale-out computation.
The SQL Server instance must have the PolyBase feature installed. PolyBase enables the integration of non-SQL Server data sources, such as Hadoop and Azure Blob Storage. See also sp_polybase_join_group.
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
sp_polybase_leave_group;
None.
0 (success) or 1 (failure).
Requires CONTROL SERVER permission.
You can only remove a compute node from a group.
After running the stored procedure, restart the PolyBase engine and PolyBase Data Movement Service on the machine. To verify, run the following DMV on the head node:
EXECUTE sys.dm_exec_compute_nodes;The example removes the current machine from a PolyBase group.
EXECUTE sp_polybase_leave_group;