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

by

Troubleshooting Guide: SQL Server Error 2023 — Metadata Not Updated for Schema-Bound Object

Why This Error Happens

This error occurs when SQL Server’s internal metadata cache becomes out of sync with a schema-bound object (such as a view, function, or computed column) after underlying base table columns are altered, dropped, or modified. It typically arises from incomplete DDL operations, interrupted transactions during schema changes, or corruption in the system metadata catalog views (sys.sysobjvalues). In some cases, this is triggered by third-party migration tools or replication processes that modify base tables without properly invoking sp_refreshview or recompiling dependent schema-bound objects.

Step-by-Step Resolution Guide

Step 1: Identify the Affected Schema-Bound Object

  • Check the full error message to extract the exact object name referenced in %ls.
  • Run the following query to locate schema-bound dependencies:
  SELECT referencing_schema_name, referencing_entity_name, referencing_class_desc
  FROM sys.dm_sql_referencing_entities('YourBaseTableName', 'OBJECT');
  • Confirm whether the object is a view, function, or indexed view using sys.objects.

Step 2: Refresh the Object Metadata

  • Execute sp_refreshsqlmodule or sp_refreshview against the affected object:
  EXEC sp_refreshview 'dbo.YourViewName';
  • For functions or stored procedures, use:
  EXEC sp_refreshsqlmodule 'dbo.YourFunctionName';
  • If the object has WITH SCHEMABINDING, you may need to drop and recreate it manually using the original CREATE script stored in source control.

Step 3: Validate Database Consistency

  • Run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to rule out catalog corruption.
  • Review the SQL Server Error Log (C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for additional context around the timestamp of the error.
  • If corruption is detected in system tables, restore the database from the last known good backup rather than attempting repairallowdata_loss on system metadata.

Step 4: Rebuild Dependent Indexed Views (If Applicable)

  • If the schema-bound object is an indexed view, drop the clustered index before refreshing:
  DROP INDEX IX_YourIndexName ON dbo.YourViewName;
  • Recreate the view definition, then rebuild the index:
  CREATE UNIQUE CLUSTERED INDEX IX_YourIndexName ON dbo.YourViewName (YourColumn);

Alternative or Verification Steps

  • Verify the fix by querying the object directly (SELECT * FROM dbo.YourViewName;) and confirming no errors are thrown, then check sys.sql_expression_dependencies to ensure dependency metadata is current.
  • If the issue persists, use SQL Server Management Studio’s Generate Scripts wizard to export and fully drop/recreate the entire object chain (base table → view → indexed view), ensuring schema binding is reapplied in the correct dependency order.