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

by

Troubleshooting Guide: SQL Server Error 8304 – INDEXKEY_PROPERTY Deprecation Warning

Why This Error Happens

Error 8304 is raised because INDEXKEY_PROPERTY has been marked as a deprecated feature in SQL Server 2025, and Microsoft has configured the Database Engine to emit this warning whenever the function is invoked in a query, stored procedure, view, or script. This occurs because legacy T-SQL code (often inherited from maintenance scripts, monitoring tools, or third-party database utilities) still references this function to retrieve index key column properties. The root cause is not a system failure but a compatibility-level flag that triggers deprecation tracking, which SQL Server uses to warn administrators before the feature is fully removed in a future release.

Step-by-Step Resolution Guide

Step 1: Identify All References to INDEXKEY_PROPERTY

  • Run a search across your database objects using the following query to locate affected code:
  • SELECT OBJECT_NAME(object_id), definition FROM sys.sql_modules WHERE definition LIKE '%INDEXKEY_PROPERTY%';
  • Check SQL Server Agent jobs, SSIS packages, and linked server scripts, as these are common hiding places for deprecated function calls.
  • Document every object that returns a match so you can prioritize remediation.

Step 2: Replace INDEXKEY_PROPERTY with Supported Catalog Views

  • Migrate existing logic to use sys.index_columns joined with sys.columns and sys.indexes, which provide the same metadata without triggering deprecation warnings.
  • Example replacement query:
  • SELECT i.name AS IndexName, c.name AS ColumnName, ic.key_ordinal, ic.is_descending_key FROM sys.indexes i INNER JOIN sys.index_columns ic ON i.object_id = ic.object_id AND i.index_id = ic.index_id INNER JOIN sys.columns c ON ic.object_id = c.object_id AND ic.column_id = c.column_id;
  • Update any application-layer ORM mappings or reporting views that depend on the old function syntax.

Step 3: Enable Deprecation Feature Tracking (Optional Monitoring)

  • Use Extended Events to confirm whether the warning still fires after code changes, by creating a session targeting the deprecation_announcement event.
  • Navigate to SQL Server Management Studio (SSMS) > Management > Extended Events > New Session, and filter on object_name = INDEXKEY_PROPERTY.
  • Let the session run for 24–48 hours in a staging environment to catch any missed references before deploying to production on Windows Server 2025.

Step 4: Update Compatibility Level and Re-test

  • Check your current database compatibility level by running SELECT name, compatibility_level FROM sys.databases WHERE name = 'YourDatabaseName';
  • If the database is running at a lower compatibility level, consider updating it incrementally (e.g., 150 to 160) using ALTER DATABASE YourDatabaseName SET COMPATIBILITY_LEVEL = 160; to align with SQL Server 2025 best practices, which often surfaces additional deprecated features earlier.
  • Re-run your regression test suite against all stored procedures and views after the compatibility change.

Alternative or Verification Steps

  • Confirm the fix by re-executing the original queries that previously generated Error 8304 and verifying the warning no longer appears in the SSMS Messages tab or the SQL Server Error Log (located at C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG by default).
  • As an alternative if full replacement isn’t immediately feasible, suppress non-critical deprecation noise temporarily by filtering Error 8304 in your monitoring/alerting tool (e.g., SQL Server Agent alerts or SCOM), while scheduling a formal code remediation sprint before the next major SQL Server upgrade.