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

by

Troubleshooting Guide: Error 1937 – Cannot Create Indexed View Due to Nested View Reference

Why This Error Happens

SQL Server 2025 enforces strict rules when creating indexed views (views with a unique clustered index), and one of those rules prohibits a view from referencing another view in its SELECT statement. This error occurs because the SQL Server query optimizer cannot resolve or materialize the schema binding correctly when a view depends on another view rather than on base tables directly. Essentially, the engine needs direct, deterministic access to underlying table structures to build and maintain the index, and an intermediate view introduces an abstraction layer it cannot bind to.

Step-by-Step Resolution Guide

Step 1: Identify the Nested View Dependency

  • Open SQL Server Management Studio (SSMS) and connect to your SQL Server 2025 instance.
  • Run sp_depends 'YourViewName'; or query sys.sql_expression_dependencies to locate exactly which referenced view is causing the conflict.
  • Note the full definition of the “inner” view (the one being referenced) using sp_helptext 'InnerViewName';.

Step 2: Expand the Referenced View Manually

  • Copy the SELECT logic from the inner view definition.
  • Paste and merge that logic directly into the CREATE VIEW statement of the outer view you are trying to index, replacing the view reference with the actual table joins/columns.
  • Ensure you use two-part naming conventions (e.g., dbo.TableName) for all referenced objects, as required for schema-binding.

Step 3: Apply Schema Binding and Validate Syntax

  • Add the WITH SCHEMABINDING option to your updated CREATE VIEW statement.
  • Verify that all aggregate functions (if any) include COUNT_BIG(*) where required, and that no SELECT * syntax is used—explicitly list column names.
  • Execute the modified script in a Query Window to confirm the view compiles without referencing the external view.

Step 4: Create the Unique Clustered Index

  • Once the view compiles successfully, run the index creation command:
  • CREATE UNIQUE CLUSTERED INDEX IX_IndexName ON dbo.YourViewName (Column1, Column2);
  • Check the Messages tab in SSMS to confirm the index was created without triggering Error 1937 again.

Alternative or Verification Steps

  • Verification: Run SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID('dbo.YourViewName'); to confirm the clustered index now exists on the view.
  • Alternative: If manually expanding the view is too complex due to multiple layers of nesting, consider using a Materialized Table (ETL approach) via a scheduled SQL Agent Job instead of an indexed view to pre-aggregate the data.