Troubleshooting Guide: Error 3874 – Resource Pool Does Not Exist

Why This Error Happens

This error occurs when a SQL Server session, workload group, or classifier function references a Resource Governor resource pool that has either been dropped or not yet applied via ALTER RESOURCE GOVERNOR RECONFIGURE. It commonly happens after a DBA creates or modifies a resource pool configuration but forgets to reconfigure the Resource Governor, leaving the in-memory metadata out of sync with the system catalog. It can also occur if a workload group is left pointing to a pool name that was renamed or removed during a maintenance script execution.

Step-by-Step Resolution Guide

Step 1: Verify the Resource Pool Exists in the Catalog

• Open SQL Server Management Studio (SSMS) or Azure Data Studio connected to your SQL Server 2025 instance.
• Run the following query to check existing pools:

  SELECT * FROM sys.resource_governor_resource_pools;

• Confirm the pool name referenced in the error message actually exists in this output.

Step 2: Reconfigure the Resource Governor

• If the pool exists but SQL Server is still throwing the error, the in-memory configuration is likely stale.
• Run the reconfiguration command to apply pending changes:

  ALTER RESOURCE GOVERNOR RECONFIGURE;

• This forces SQL Server 2025 to sync the active configuration with the pending changes in sys.resource_governor_configuration.

Step 3: Recreate the Missing Resource Pool

• If the pool genuinely does not exist (was dropped or never created), recreate it manually:

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

• Ensure the workload group mapping is also updated to point to the correct pool name:

  ALTER WORKLOAD GROUP [YourWorkloadGroup] USING [YourPoolName];
  ALTER RESOURCE GOVERNOR RECONFIGURE;

Step 4: Check Classifier Function Logic

• Open the classifier user-defined function (UDF) assigned to Resource Governor.
• Confirm it does not hardcode a resource pool/workload group name that was deleted or renamed.
• Update the function logic and redeploy if a stale reference is found:

  ALTER RESOURCE GOVERNOR WITH (CLASSIFIER_FUNCTION = dbo.YourClassifierFunction);
  ALTER RESOURCE GOVERNOR RECONFIGURE;

Step 5: Restart the SQL Server Service (If Necessary)

• On Windows Server 2025 / Windows 11, open Services.msc.
• Locate SQL Server (MSSQLSERVER) or your named instance.
• Right-click and select Restart to fully clear any cached Resource Governor metadata if reconfiguration alone does not resolve it.

Alternative or Verification Steps

• Run SELECT * FROM sys.dm_resource_governor_resource_pools; to confirm the pool is now active in the live Resource Governor state and matches your catalog configuration.
• If the error persists after recreating the pool and reconfiguring, disable Resource Governor temporarily with ALTER RESOURCE GOVERNOR DISABLE;, then re-enable it after validating all pool/workload group definitions are consistent.