You will create an operational policy for your virtual SQL Server instances, where only these settings differ from the main production policy. In this policy, you change the memory and CPU settings for specific objects. You then configure vRealize Operations Manager to send alerts to you when the performance degrades on your virtual SQL Servers.

In this procedure, you create a dedicated policy for a subset of virtual SQL Server objects, and change settings for the memory and CPU capacity for your virtual SQL Server instances. At this point in the scenario, your custom policy has only minor differences from the production policy.

The difference between the main production policy and your virtual SQL Server policy is in the overcommitment of compute resources. For the SQL Server policy, you do not overcommit compute resources. You have the SQL server policy inherit most of the settings from your overall production policy, except that you change the capacity settings that apply directly to the virtual SQL servers.

After you apply the main production policy to your entire production environment, you create the dedicated policy, have it inherit settings from the main policy, and make minor changes to settings in the dedicated policy to adjust the capacity levels for your virtual SQL Servers.

To create this policy, you choose a cluster that contains the data center and the vCenter Server that will use this policy. You make minor changes for all of the objects, including the cluster, data center, host system, resource pools, and the virtual machine resource containers.

Verify that the following conditions are met:

You know the vSphere operational requirements. See User Scenario: Determine the vSphere Operational Requirements.

A default policy is in effect for your entire production environment of vSphere objects.


In vRealize Operations Manager, select Administration > Policies.

The Active Policies tab displays the current policies in effect.


Click the Policy Library tab, and click the plus sign to add a custom policy.


In the workspace navigation pane, click Getting Started and define the basic information for the policy.


In the Name text box, enter vSphere Production Virtual SQL Servers.


In the Description text box, enter Analyze capacity of virtual SQL Servers.


To start with a base policy, select Default Policy from the Start with drop-down menu.


View the policy configuration settings.


In the policy workspace, click Select Base Policies.


To view the policy configuration for virtual machine objects, click the Show changes for drop-down menu, click vCenter Adapter - Virtual Machine, and click the Show object type filter.

The Virtual Machine policy configuration appears in the right pane.


To view the inherited settings, in the Policy Preview pane, click Configuration inherited from base policy.


In the workspace navigation, click Analysis Settings.


In the workspace navigation, add the following object types to the list so that you can change their settings.


Click the drop-down arrow, click vCenter Adapter - Cluster Compute Resource, and click the filter.


Click the drop-down arrow, click vCenter Adapter - Data Center, and click the filter.


Click the drop-down arrow, click vCenter Adapter - Host System, and click the filter.


Click the drop-down arrow, click vCenter Adapter - Resource Pool, and click the filter.


Click the drop-down arrow, click vCenter Adapter - Virtual Machine, and click the filter.

The analysis settings for these object types appear in the right pane.


On the Cluster Compute Resource bar, click the double arrows to expand the list of analysis settings.


Locate Capacity Remaining Time Remaining and click the lock button to enable changes.


In the resource table, set the overcommit for Memory Allocation value to 0 so that vRealize Operations Manager does not overcommit these objects for your SQL Server policy.


In the resource table, set the overcommit ratio for CPU Allocation to 2 so that vRealize Operations Manager overcommits a 2:1 ratio for CPU allocation on each SQL Server.


Repeat Step 7 through Step 10 for each object type that you added to the right pane.


Click Save.

You created a policy and made minor changes to settings so that vRealize Operations Manager can analyze and report on your SQL Server objects.

Configure the alert definitions and symptom definitions for your SQL Server policy. You will apply the policy to your SQL Server object groups.