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

by

Troubleshooting Guide: SQL Server Error 11425 — Concurrent Column Operation Conflict

Why This Error Happens

Error 11425 occurs when a DDL operation (such as ALTER TABLE, index rebuild, or schema change) attempts to reference a column that is currently locked by an in-progress online ALTER COLUMN operation. SQL Server 2025 enforces metadata-level locking during online schema changes to maintain consistency, and a second concurrent operation targeting the same column will be rejected rather than queued. This typically happens in high-concurrency environments where automated deployment scripts, ORM migrations, or maintenance jobs fire overlapping schema changes against the same table without proper serialization.

Step-by-Step Resolution Guide

Step 1: Identify the Conflicting Session

  • Open SQL Server Management Studio (SSMS) or Azure Data Studio connected to the affected instance.
  • Run the following query to find active online index/column operations:
  SELECT session_id, command, status, percent_complete, start_time
  FROM sys.dm_exec_requests
  WHERE command LIKE '%ONLINE%' OR command LIKE '%ALTER%';
  • Cross-reference with sys.dm_tran_locks filtered by resource_type = 'OBJECT' to confirm which session holds the schema modification lock (Sch-M) on the target table.

Step 2: Wait for or Safely Terminate the Blocking Operation

  • If the online ALTER COLUMN operation is legitimate and near completion, allow it to finish naturally rather than killing it, since online operations can be resource-intensive to restart.
  • If the operation appears stuck or abandoned, terminate it safely:
  KILL <session_id>;
  • Confirm rollback completion by monitoring sys.dm_exec_requests for status = 'rollback' before re-issuing your DDL command.

Step 3: Serialize Future DDL Executions

  • Update deployment pipelines (e.g., Azure DevOps, Jenkins, or SSDT publish profiles) to execute schema migrations sequentially rather than in parallel threads.
  • Add an explicit application lock in your migration scripts to prevent overlapping execution:
  EXEC sp_getapplock @Resource = 'TableSchemaChange_YourTableName', 
                      @LockMode = 'Exclusive', 
                      @LockOwner = 'Session';
  • Release the lock with sp_releaseapplock once the DDL statement completes.

Step 4: Validate SQL Server 2025 Resource Governor Settings (If Applicable)

  • Navigate to SQL Server Management Studio > Management > Resource Governor and check if a custom workload group is throttling concurrent DDL threads unexpectedly.
  • On Windows Server 2025/Windows 11 hosts, confirm the SQL Server service account has sufficient CPU/memory allocation in Task Manager > Details to prevent operation timeouts that leave locks in an inconsistent state.

Alternative or Verification Steps

  • Re-run the original ALTER TABLE or DDL statement after confirming (via Step 1’s query) that no sessions show ALTER COLUMN or ONLINE in their command text — a clean result set confirms the lock has cleared.
  • If the error persists despite no visible blocking session, restart the SQL Server service via Services.msc (Windows Server 2025) to clear any orphaned metadata locks, then re-attempt the schema change during a low-traffic maintenance window.