| title | Policy-Based Management Storage | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 08/10/2017 | |
| ms.prod | sql-server-2014 | |
| ms.reviewer | ||
| ms.technology | security | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | d0cbf214-fc2e-4917-8d31-1d71c9ffa61d | |
| author | MikeRayMSFT | |
| ms.author | mikeray | |
| manager | craigg |
Policies are stored in the msdb database. After a policy or condition is changed, msdb should be backed up. For more information, see Back Up and Restore of System Databases (SQL Server).
[!INCLUDEssCurrent] includes policies that can be used to monitor an instance of [!INCLUDEssNoVersion]. By default, these policies are not installed on the [!INCLUDEssDE]; however, they can be imported from the default installation location of C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Policies\DatabaseEngine\1033.
You can directly create policies by using the File/New menu, and then saving them to a file. This enables you to create policies when you are not connected to an instance of the [!INCLUDEssDE].
Policy history for policies evaluated in the current instance of the [!INCLUDEssDE] is maintained in msdb system tables. Policy history for policies applied to other instances of the [!INCLUDEssDE] or applied to [!INCLUDEssRSnoversion] or [!INCLUDEssASnoversion] is not retained.