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

by

Troubleshooting Guide: Error 932 – Change Tracking Not Supported by SQL Server Edition

Why This Error Happens

This error occurs because the database being attached or restored has Change Tracking enabled, but the current instance of SQL Server 2025 is running on an edition (such as Express or Web Edition) that does not support this feature. SQL Server performs an edition-compatibility check during database load, and since Change Tracking metadata exists in the database schema, the engine blocks the load to prevent corruption or unsupported feature usage. This typically happens after migrating a database from Standard or Enterprise Edition down to a lower-tier edition.

Step-by-Step Resolution Guide

Step 1: Verify the Current SQL Server Edition

  • Open SQL Server Management Studio (SSMS) and connect to the instance.
  • Run the following query to check the installed edition:
  SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS Version;
  • Confirm whether the edition is Express, Web, or another edition that lacks Change Tracking support (only Standard, Enterprise, and Developer editions support it).

Step 2: Disable Change Tracking on the Source Database (Before Migration)

  • If you still have access to the original higher-edition instance, disable Change Tracking before moving the database.
  • Run these commands on the source server:
  ALTER DATABASE [YourDatabaseName] SET CHANGE_TRACKING = OFF;
  • If tracking is enabled on specific tables, disable it there first:
  ALTER TABLE [YourTable] DISABLE CHANGE_TRACKING;
  • Re-export or back up the database after disabling tracking.

Step 3: Upgrade to a Supported Edition (If Source Access Is Unavailable)

  • If you cannot modify the source database, install or upgrade to SQL Server 2025 Standard, Enterprise, or Developer Edition on Windows Server 2025 / Windows 11.
  • Use the SQL Server Installation Center to perform an Edition Upgrade:
  Setup.exe /ACTION=EditionUpgrade /INSTANCENAME=MSSQLSERVER /PID=<NewProductKey>
  • Restart the SQL Server service via services.msc or:
  Restart-Service -Name 'MSSQLSERVER'

Step 4: Reattach or Restore the Database

  • After confirming the edition supports Change Tracking, reattach or restore the database:
  RESTORE DATABASE [YourDatabaseName] FROM DISK = 'C:\Backups\YourDatabase.bak' WITH REPLACE;
  • Monitor the SQL Server Error Log (Management > SQL Server Logs in SSMS) to confirm no further Error 932 entries appear.

Alternative or Verification Steps

  • Verify the fix: Run SELECT * FROM sys.change_tracking_databases; to confirm Change Tracking status is correctly reflected and the database loads without error.
  • Alternative fix: If upgrading the edition is not feasible, script out the database schema and data (excluding Change Tracking objects) using the Generate Scripts Wizard in SSMS, then import it into the lower-edition instance manually.