| title | sp_syspolicy_add_policy_category (Transact-SQL) | ||
|---|---|---|---|
| description | Adds a policy category that can be used with Policy-Based Management. | ||
| author | VanMSFT | ||
| ms.author | vanto | ||
| ms.reviewer | randolphwest | ||
| ms.date | 06/23/2025 | ||
| ms.service | sql | ||
| ms.subservice | system-objects | ||
| ms.topic | reference | ||
| f1_keywords |
|
||
| helpviewer_keywords |
|
||
| dev_langs |
|
[!INCLUDE SQL Server]
Adds a policy category that can be used with Policy-Based Management. Policy categories enable you to organize policies, and to set policy scope.
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
sp_syspolicy_add_policy_category
[ @name = ] N'name'
[ , [ @mandate_database_subscriptions = ] mandate_database_subscriptions ]
, [ @policy_category_id = ] policy_category_id OUTPUT
[ ; ]
The name of the policy category. @name is sysname, and is required. @name can't be NULL or an empty string.
Determines whether database subscription is mandated for the policy category. @mandate_database_subscriptions is bit value, with a default of 1 (enabled).
The identifier for the policy category. @policy_category_id is int, and is returned as OUTPUT.
0 (success) or 1 (failure).
You must run sp_syspolicy_add_policy_category in the context of the msdb system database.
Requires membership in the PolicyAdministratorRole fixed database role.
[!INCLUDE policy-administrator-role]
The following example creates a policy category where subscription to the category isn't mandated. This means that individual databases can be configured to opt in or opt out of policies in the category.
DECLARE @policy_category_id AS INT;
EXECUTE msdb.dbo.sp_syspolicy_add_policy_category
@name = N'Table Naming Policies',
@mandate_database_subscriptions = 0,
@policy_category_id = @policy_category_id OUTPUT;
GO