Resource Management with Resource Governor - Microsoft SQL Server 2012 Performance Tuning - page 430

Finally, we see the Resource Governor objects created in Object Explorer, under the
Resource Governor node.
There's more...
In the real world, before implementing Resource Governor, you should do a trend analysis on
resource requirements for various applications. This will help you in setting proper resource
pool parameter values.
Resource pools are configured based on the following parameters:
F MIN_CPU_PERCENT
F MAX_CPU_PERCENT
F MIN_MEMORY_PERCENT
F MAX_MEMORY_PERCENT
The percentage of resources specified by MIN parameters is not shared by multiple resource
pools, and the MIN parameter values for CPU and memory specify the minimum percentage of
resources guaranteed. There can be multiple resource pools in Resource Governor. This is the
reason why the total of all MIN percent values across all resource pools cannot exceed 100.
On the other hand, the percentage of resources as specified by MAX parameters is shared
across multiple resource pools, and the effective MAX values are adjusted if the MIN values
for any resource pools are increased or decreased.
In SQL Server 2012, Resource Governor introduced a new parameter
called CAP_CPU_PERCENT . The value of this parameter specifies a
hard cap for CPU bandwidth and it limits the maximum CPU usage to
the specified value for all the requests in the resource pool.
Configuring Resource Governor with T-SQL
script
In the previous recipe, we learnt how to enable/configure Resource Governor and create
workload groups and resource pools, using SQL Server Management Studio.
However, DBAs always love to work with scripts. The reason is that scripts are scalable and
reusable. They can be executed on different servers to create identical objects. They can even
be executed without opening SQL Server Management Studio, with a utility such as SQLCMD.