Troubleshooting Guide: Error 10911 – Resource Pool Does Not Exist

Why This Error Happens

This error occurs when a T-SQL statement, application connection string, or Resource Governor classifier function references a resource pool name that does not currently exist in the SQL Server instance’s configuration. This commonly happens after a resource pool was dropped or renamed but dependent objects (like workload group mappings or classifier functions) were not updated to match. It can also occur during migration or restore operations where Resource Governor configurations from a source server do not fully apply to the destination server in SQL Server 2025.

Step-by-Step Resolution Guide

Step 1: Verify Existing Resource Pools

• Open SQL Server Management Studio (SSMS) and connect to the SQL Server 2025 instance.
• Run the following query to list all currently configured resource pools:

SELECT name, pool_id FROM sys.resource_governor_resource_pools;

• Confirm whether the resource pool name referenced in your application, script, or error message actually exists in this list.

Step 2: Recreate the Missing Resource Pool

• If the resource pool was accidentally dropped, recreate it using the CREATE RESOURCE POOL statement.
• Example syntax:

CREATE RESOURCE POOL [YourPoolName]
WITH (
    MIN_CPU_PERCENT = 0,
    MAX_CPU_PERCENT = 100,
    MIN_MEMORY_PERCENT = 0,
    MAX_MEMORY_PERCENT = 100
);
ALTER RESOURCE GOVERNOR RECONFIGURE;

• Ensure the pool name matches exactly (case-sensitive in some collations) with what is referenced in the workload group or classifier function.

Step 3: Update Workload Group and Classifier Function References

• Check the sys.resource_governor_workload_groups system view to confirm the workload group is pointing to a valid, existing pool_id.
• If using a custom classifier function (sys.fn_classifier), open the function definition and search for hardcoded resource pool names.
• Update any stale references to match the current resource pool name, then run ALTER RESOURCE GOVERNOR RECONFIGURE; to apply changes.

Step 4: Check SQL Server Error Logs and Configuration Scripts

• Navigate to the SQL Server error log directory, typically located at:
  C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG
• Search for entries related to “Resource Governor” to identify exactly which script or startup process triggered Error 10911.
• If this occurred during a server migration, review any exported Resource Governor DDL scripts for naming mismatches before re-running them.

Alternative or Verification Steps

• To verify the fix, re-run the original failing query or application connection and confirm Error 10911 no longer appears in SSMS or the Windows Event Viewer.
• As an alternative, if the pool name is genuinely obsolete, update the classifier function or application connection string to point to the default resource pool instead of recreating a custom one.