| title | DROP WORKLOAD GROUP (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 11/04/2019 | ||
| ms.prod | sql | ||
| ms.prod_service | sql-database | ||
| ms.reviewer | |||
| ms.technology | t-sql | ||
| ms.topic | language-reference | ||
| f1_keywords |
|
||
| dev_langs |
|
||
| helpviewer_keywords |
|
||
| author | CarlRabeler | ||
| ms.author | carlrab | ||
| monikerRange | >=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azure-sqldw-latest||=azuresqldb-mi-current |
In the following row, click whichever product name you're interested in. The click displays different content here on this webpage, appropriate for whichever product you click.
::: moniker range=">=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current||=sqlallproducts-allversions"
* SQL Server * SQL Database
managed instanceSQL Data
Warehouse
Drops an existing user-defined Resource Governor workload group.
Transact-SQL Syntax Conventions.
DROP WORKLOAD GROUP group_name
[;]
group_name
Is the name of an existing user-defined workload group.
The DROP WORKLOAD GROUP statement is not allowed on the Resource Governor internal or default groups.
When you are executing DDL statements, we recommend that you be familiar with Resource Governor states. For more information, see Resource Governor.
If a workload group contains active sessions, dropping or moving the workload group to a different resource pool will fail when the ALTER RESOURCE GOVERNOR RECONFIGURE statement is called to apply the change. To avoid this problem, you can take one of the following actions:
-
Wait until all the sessions from the affected group have disconnected, and then rerun the ALTER RESOURCE GOVERNOR RECONFIGURE statement.
-
Explicitly stop sessions in the affected group by using the KILL command, and then rerun the ALTER RESOURCE GOVERNOR RECONFIGURE statement.
-
Restart the server. After the restart process is completed, the deleted group will not be created, and a moved group will use the new resource pool assignment.
-
In a scenario in which you have issued the DROP WORKLOAD GROUP statement but decide that you do not want to explicitly stop sessions to apply the change, you can re-create the group by using the same name that it had before you issued the DROP statement, and then move the group to the original resource pool. To apply the changes, run the ALTER RESOURCE GOVERNOR RECONFIGURE statement.
Requires CONTROL SERVER permission.
The following example drops the workload group named adhoc.
DROP WORKLOAD GROUP adhoc;
GO
ALTER RESOURCE GOVERNOR RECONFIGURE;
GO
Resource Governor
CREATE WORKLOAD GROUP (Transact-SQL)
ALTER WORKLOAD GROUP (Transact-SQL)
CREATE RESOURCE POOL (Transact-SQL)
ALTER RESOURCE POOL (Transact-SQL)
DROP RESOURCE POOL (Transact-SQL)
ALTER RESOURCE GOVERNOR (Transact-SQL)
::: moniker-end ::: moniker range="=azure-sqldw-latest||=sqlallproducts-allversions"
SQL Server SQL Database
managed instance
Drops a workload group. Once the statement completes, the settings are in effect.
Transact-SQL Syntax Conventions.
DROP WORKLOAD GROUP group_name
group_name
Is the name of an existing user-defined workload group.
A workload group cannot be dropped if classifiers exist for the workload group. Drop the classifiers before the workload group is dropped. If there are active requests using resources from the workload group being dropped, the drop workload statement is blocked behind them.
Use the following code example to determine which classifiers need to be dropped before the workload group can be dropped.
SELECT c.name as classifier_name
,'DROP WORKLOAD CLASSIFIER '+c.name as drop_command
FROM sys.workload_management_workload_classifiers c
JOIN sys.workload_management_workload_groups g
ON c.group_name = g.name
WHERE g.name = 'wgXYZ' --change the filter to the workload being droppedRequires CONTROL DATABASE permission
CREATE WORKLOAD GROUP (Transact-SQL)
::: moniker-end