Operation failed. The index entry of length %d bytes for the index ‘%.*ls’ exceeds the maximum length of %d bytes.

Error Message:
Msg 1946, Level 16, State 3, Line 10
Operation failed. The index entry of length %d bytes for the index ‘%.*ls’ exceeds the maximum length of %d bytes.

Severity level:
16.

Description:
This error message appears when you try to insert or update a row and an index entry exceeds the maximum allowed length of 900 bytes.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Errors of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. The maximum allowed length for index entries is 900 bytes.

Versions:
All versions of SQL Server.

Example(s):
IF OBJECT_ID (‘dbo.t’) IS NOT NULL
    DROP TABLE dbo.t;
GO
CREATE TABLE dbo.t (s1 varchar(1000) PRIMARY KEY);

INSERT INTO dbo.t SELECT REPLICATE (‘a’, 900);

SELECT
    *
FROM
    dbo.t;
    
UPDATE dbo.t
    SET
    s1 = s1 + ‘b’;

Remarks:
In the above example we first create the table dbo.t. During creation you get the informell error message 1945. The following INSERT statement runs error-free, but the UPDATE statement exceeds the maximum length of 900 bytes and raises the error.



Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |