Troubleshooting Guide: SQL Server Error 11429 — Online ALTER COLUMN Failure Due to Change Tracking or Merge Replication

Why This Error Happens

This error occurs because SQL Server’s online ALTER COLUMN feature is architecturally incompatible with tables that have change tracking enabled or are configured for merge replication, since both features rely on internal metadata and triggers that conflict with the online schema modification process. SQL Server 2025 performs a pre-validation check before executing the ALTER COLUMN operation, and when it detects either feature active on the target table, it blocks the online variant of the operation to prevent data consistency issues or metadata corruption. The fix requires either temporarily disabling these features, performing the operation offline, or restructuring your approach to schema changes on tracked/replicated tables.

Step-by-Step Resolution Guide

Step 1: Identify Which Feature Is Causing the Conflict

Open SQL Server Management Studio (SSMS) and connect to your SQL Server 2025 instance.
Run the following query to check if change tracking is enabled on the table:

  SELECT * FROM sys.change_tracking_tables 
  WHERE object_id = OBJECT_ID('YourSchema.YourTableName');

Run this query to check for merge replication involvement:

  SELECT * FROM sys.sysmergearticles 
  WHERE nick_name = (SELECT nickname FROM sys.sysmergeschemachange 
  WHERE art_nick = OBJECT_ID('YourSchema.YourTableName'));

Confirm which feature (or both) is active before proceeding.

Step 2: Disable Change Tracking (If Applicable)

Execute the following T-SQL command to disable change tracking on the affected table:

  ALTER TABLE YourSchema.YourTableName DISABLE CHANGE_TRACKING;

If change tracking is enabled at the database level and no longer needed, also run:

  ALTER DATABASE YourDatabaseName SET CHANGE_TRACKING = OFF;

Verify the service account has ALTER permission on the table before running this command.

Step 3: Disable Merge Replication (If Applicable)

Open SSMS, navigate to Replication > Local Publications, and locate the publication containing the affected table.
Right-click the publication and select Delete or remove the specific article tied to your table using:

  EXEC sp_dropmergearticle @publication = 'YourPublicationName', @article = 'YourTableName';

Alternatively, drop the entire merge publication if it is no longer required:

  EXEC sp_dropmergepublication @publication = 'YourPublicationName';

Step 4: Perform the ALTER COLUMN Operation

With change tracking and/or merge replication disabled, re-run your original ALTER COLUMN statement:

  ALTER TABLE YourSchema.YourTableName 
  ALTER COLUMN YourColumnName NVARCHAR(255) WITH (ONLINE = ON);

Confirm the command completes without Error 11429 in the Messages pane.

Step 5: Re-enable Change Tracking or Replication (If Needed)

If change tracking is required for application functionality, re-enable it post-alteration:

  ALTER TABLE YourSchema.YourTableName ENABLE CHANGE_TRACKING;

Reconfigure merge replication publications/articles through the New Publication Wizard in SSMS if replication must resume.

Alternative or Verification Steps

To verify the fix, re-run the sys.change_tracking_tables and sys.sysmergearticles queries from Step 1 to confirm the table’s status, then execute the ALTER COLUMN statement again to ensure it completes successfully without Error 11429.
If disabling these features is not feasible due to business constraints, perform the ALTER COLUMN operation offline by omitting the WITH (ONLINE = ON) clause — note this will briefly lock the table, so schedule it during a maintenance window.