DROP WORKLOAD GROUP (Transact-SQL)
Applies To: SQL Server 2014, SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Drops an existing user-defined Resource Governor workload group.
Applies to: SQL Server (SQL Server 2008 through current version).
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.
The following example drops the workload group named adhoc.
DROP WORKLOAD GROUP adhoc; GO ALTER RESOURCE GOVERNOR RECONFIGURE; GO