Troubleshooting Guide: SQL Server Error 7672 – Duplicate Column Specified in Full-Text Index

Why This Error Happens

This error occurs when the CREATE FULLTEXT INDEX or ALTER FULLTEXT INDEX ADD statement references the same column name more than once in the column list. It can also surface when a column is specified both explicitly and implicitly through an alias or a case-insensitive duplicate (e.g., Notes and notes being treated as the same underlying column). In some cases, this is triggered by automation scripts or ORM-generated DDL that dynamically builds column lists without checking for existing entries, resulting in the same column being appended twice.

Step-by-Step Resolution Guide

Step 1: Review the Exact T-SQL Statement Causing the Error

• Open SQL Server Management Studio (SSMS) and locate the script or stored procedure that issued the CREATE FULLTEXT INDEX command.
• Check the full error message for the specific column name reported in the %.*ls placeholder — this tells you exactly which column is duplicated.
• Example problematic syntax:

  CREATE FULLTEXT INDEX ON dbo.Documents(Title, Body, Title)
  KEY INDEX PK_Documents ON ftCatalog;

Step 2: Clean Up the Column List

• Remove the duplicate column reference, keeping only a single instance of each column name.
• If the index was built dynamically (via PowerShell, dbatools, or a deployment pipeline), inspect the script logic that generates the column array/list.
• Corrected syntax example:

  CREATE FULLTEXT INDEX ON dbo.Documents(Title, Body)
  KEY INDEX PK_Documents ON ftCatalog;

Step 3: Check for Existing Full-Text Index Columns Before Re-Adding

• If you are using ALTER FULLTEXT INDEX ADD (ColumnName), first query the existing full-text columns to avoid re-adding one that is already indexed:

  SELECT c.name AS ColumnName
  FROM sys.fulltext_index_columns AS fic
  INNER JOIN sys.columns AS c
      ON fic.object_id = c.object_id AND fic.column_id = c.column_id
  WHERE fic.object_id = OBJECT_ID('dbo.Documents');

• Remove any column from your ADD statement that already appears in this result set.

Step 4: Drop and Recreate the Full-Text Index (If Corrupted Metadata Is Suspected)

• If duplicates persist despite a clean script (possible metadata corruption), drop the existing full-text index entirely:

  DROP FULLTEXT INDEX ON dbo.Documents;

• Recreate it from scratch with a verified, de-duplicated column list, specifying the correct KEY INDEX and catalog on your Windows Server 2025 instance.

Alternative or Verification Steps

• Verify the fix by running SELECT * FROM sys.fulltext_index_columns WHERE object_id = OBJECT_ID('dbo.Documents'); and confirming each column_id appears only once.
• If the issue persists in automated deployment pipelines, add a DISTINCT or de-duplication filter (e.g., Set collection in PowerShell) in the script that generates the column list before it reaches SQL Server.