Skip to content

Latest commit

 

History

History
61 lines (41 loc) · 2.86 KB

evaluate-policies-dialog-box-policy-selection-page.md

File metadata and controls

61 lines (41 loc) · 2.86 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic f1_keywords
'Policy Selection' page of the 'Evaluate Policies' dialog box
Describes the 'Policy Selection' page of the 'Evaluate Policies' dialog box for Policy-Based Management in SQL Server Management Studio (SSMS).
VanMSFT
vanto
12/15/2023
sql
security
ui-reference
sql13.swb.dmf.runnow.f1

Evaluate Policies dialog box, Policy Selection page

[!INCLUDE SQL Server]

Use this dialog box to evaluate Policy-Based Management policies. By selecting the Evaluation Results page, you can apply policies to the items in a target set that doesn't comply with the policies.

Options

Source
Specifies the source of the policies. To change the source, select the Browse (...) button to open the Select Source dialog box.

Files
Type the path of a file that contains a Policy-Based Management policy, or use the Browse (...) button to select the file.

Server
Select to connect to an instance of the [!INCLUDE ssDEnoversion] that contains the policy that you want.

Policies: Policy
Select to open the policy dialog box for the specified policy.

Policies: Category
The category of the policy. This box is read-only.

Policies: Facet
The facet implemented by the policy. This box is read-only.

Evaluate
Runs the policy in evaluation mode. This generates a compliance report for the target set but doesn't reconfigure [!INCLUDE ssNoVersion] or enforce future compliance.

Possible errors

  • No targets found

    The target set could be empty due to any of the following reasons:

    • There are no targets on the instance of [!INCLUDE ssNoVersion] of the type specified by the policy.

    • The server restriction might exclude the instance of [!INCLUDE ssNoVersion] that contains the target.

    • If the policy is on an object in a database (for example a table, view, or user) the database might not subscribe to the category of the policy.

    • The target-set filter might exclude all targets on this instance of [!INCLUDE ssNoVersion].

    • The target server type is different from the server type on which the policy is evaluated. For example, in the [!INCLUDE ssDE], if you try to evaluate a policy that has been created for [!INCLUDE ssASnoversion], you'll receive an empty target set.

Related content