The Marketing department also has a CPU-intensive workload, but has lower-priority queries. The Sales department has a CPU-intensive workload with high-priority queries. For example, assume the Sales and Marketing departments in a company share the same database. You can use these settings to establish predictable CPU resource usage for multiple workloads that is based on the needs of each workload. These settings are the minimum and maximum guaranteed average CPU bandwidth for all requests in the resource pool when there is CPU contention.
The pool resources are defined by specifying one or more of the following settings for each resource (CPU, memory, and physical IO): The other part is shared with other pools, which supports maximum possible resource consumption. One part does not overlap with other pools, which enables minimum resource reservation. You can think of a pool as a virtual SQL Server instance inside of a SQL Server instance. Resource Pool ConceptsĪ resource pool, or pool, represents the physical resources of the server. When a session is started, the Resource Governor classifier assigns the session to a specific workload group, and the session must run using the resources assigned to the workload group. Each resource pool can contain one or more workload groups. Resource Governor enables you to specify limits on the amount of CPU, physical IO, and memory that incoming application requests can use within the resource pool.
In the SQL Server Resource Governor, a resource pool represents a subset of the physical resources of an instance of the Database Engine.
Applies to: SQL Server (all supported versions) Azure SQL Managed Instance