| title | sp_syspolicy_set_log_on_success (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 08/09/2016 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine | ||
| ms.reviewer | |||
| ms.technology | system-objects | ||
| ms.topic | language-reference | ||
| f1_keywords |
|
||
| dev_langs |
|
||
| helpviewer_keywords |
|
||
| ms.assetid | 6b33383b-5949-488a-a911-59299a270f46 | ||
| author | VanMSFT | ||
| ms.author | vanto |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]
Specifies whether successful policy evaluations are logged in the Policy History log for Policy-Based Management.
Transact-SQL Syntax Conventions
sp_syspolicy_set_log_on_success [ @value = ] value
[ @value = ] value
Determines whether successful policy evaluations are logged. value is sqlvariant, and can be one of the following values:
-
0 or 'false' = Successful policy evaluations are not logged.
-
1 or 'true' = Successful policy evaluations are logged.
0 (success) or 1 (failure)
You must run sp_syspolicy_set_log_on_success in the context of the msdb system database.
When value is set to 0 or to 'false', only failed policy evaluations are logged.
Requires membership in the PolicyAdministratorRole fixed database role.
IMPORTANT!! Possible elevation of credentials: Users in the PolicyAdministratorRole role can create server triggers and schedule policy executions that can affect the operation of the instance of the [!INCLUDEssDE]. For example, users in the PolicyAdministratorRole role can create a policy that can prevent most objects from being created in the [!INCLUDEssDE]. Because of this possible elevation of credentials, the PolicyAdministratorRole role should be granted only to users who are trusted with controlling the configuration of the [!INCLUDEssDE].
The following example enables the logging of successful policy evaluations.
EXEC msdb.dbo.sp_syspolicy_set_log_on_success @value = 1;
GO
Policy-Based Management Stored Procedures (Transact-SQL)
sp_syspolicy_configure (Transact-SQL)