How to fix Error 10929 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 10929 – Resource Governor Memory Limit

Why This Error Happens

Error 10929 occurs when the Resource Governor in SQL Server 2025 enforces a workgroup memory limit that has been configured too restrictively for the current workload. This typically happens when MAX_MEMORY_PERCENT or REQUEST_MAX_MEMORY_GRANT_PERCENT settings in a Resource Pool are set too low relative to actual query memory demands. The error can also surface after a server migration or configuration import where Resource Governor pool settings were not recalibrated for the new hardware’s available memory.

Step-by-Step Resolution Guide

Step 1: Identify the Offending Resource Pool

  • Run the following query to find the Resource ID referenced in the error message:
  • SELECT * FROM sys.dm_resource_governor_resource_pools WHERE pool_id = <Resource ID from error>;
  • Note the min_memory_percent and max_memory_percent values currently assigned.
  • Cross-reference this with sys.resource_governor_resource_pools to see the persisted configuration versus the in-memory runtime state.

Step 2: Recalculate Memory Allocation Across Pools

  • Ensure the sum of MIN_MEMORY_PERCENT across all resource pools does not exceed 100%.
  • On Windows Server 2025/Windows 11 hosts, confirm the SQL Server instance’s “Max server memory” setting isn’t artificially capping the pool below its configured minimum guarantee.
  • Adjust the pool using T-SQL:
  • ALTER RESOURCE POOL [PoolName] WITH (MIN_MEMORY_PERCENT = 0, MAX_MEMORY_PERCENT = 100);
  • ALTER RESOURCE GOVERNOR RECONFIGURE;

Step 3: Review Workload Group Settings

  • Check REQUEST_MAX_MEMORY_GRANT_PERCENT on the Workload Group tied to the pool, as an overly aggressive single-query grant request can trigger this even with correct pool-level settings.
  • Lower this value if a single runaway query or reporting job is monopolizing the pool’s guarantee.
  • Use sp_configure 'show advanced options', 1; followed by RECONFIGURE; to ensure advanced settings are visible before altering memory options.

Step 4: Restart the Resource Governor Service Context

  • Execute ALTER RESOURCE GOVERNOR RECONFIGURE; to apply changes without a full service restart.
  • If the error persists, restart the SQL Server service via Windows Services (services.msc) or net stop MSSQLSERVER && net start MSSQLSERVER to clear any cached memory broker states.

Alternative or Verification Steps

  • Verify the fix by querying sys.dm_resource_governor_resource_pools again and confirming the target_memory_kb aligns with the min_memory_percent without throwing allocation errors during peak load.
  • If the issue persists despite configuration changes, disable Resource Governor temporarily using ALTER RESOURCE GOVERNOR DISABLE; to confirm the error is isolated to governor settings rather than physical RAM exhaustion on the Windows Server 2025 host.