Databases Reference
In-Depth Information
FIGURE 16-1
6. Right-click on Policy and choose Create New Policy.
7. Specify the policy name Database - Auto Close .
8. Using the Check condition drop-down list, select the Auto Close Disabled condition.
9. Verify that the Against Targets options shows a check alongside Every Database.
10. Ensure that the Evaluation Mode shows On demand, and Server restriction is None.
11. Click OK.
Now expand the policies folder, right-click on the policy named Database - Auto Close, and choose
Evaluate. The report will display a list containing one row for each database on the instance, and
hopefully each will display a green check indicating compliance. Enable the Auto Close option for
one database and then reevaluate the policy to coni rm it is functioning correctly.
Now you should see a single database listed with a red cross mark, indicating noncompliance.
Alongside the noncompliant database is a checkbox; mark this checkbox as enabled. Then click the
Apply button in the lower-right corner of the dialog. Clicking the Apply button does two things: It
changes the database property to Disable Auto Close, and it reevaluates the policy to show a compli-
ant database (green) now.
This example demonstrates how effective PBM can be in identifying and resolving coni guration issues
within an environment. If this policy were scheduled, it could i nd and i x any sub-optimal coni gura-
tion within an environment. A clear benei t of this level of automation is that if any new coni guration
issue is introduced — either through a change to an existing database or through a new database in
the environment — compliance could be ensured on the next policy evaluation.
Search WWH ::




Custom Search