544 SQL Origin: Data OSI layer 7 · Application Last updated 12 Oct 2026

SQL Server: Cannot insert explicit value for identity column in table 'x' when IDENTITY_INSERT is set to OFF.

An INSERT supplied a value for an IDENTITY column.

Exact message you may see Cannot insert explicit value for identity columnIDENTITY_INSERT is set to OFF
Seen on: SQL

Meaning

Identity values are generated automatically. Imports/ORMs sending Id = 0 or explicit ids fail unless IDENTITY_INSERT is ON for that table.

Common causes

  • ORM sending a default Id (0)
  • Data migration copying ids
  • Insert lists including the identity column

⚡ Quick fix

  1. Omit the identity column from INSERT
  2. For migrations: SET IDENTITY_INSERT dbo.T ON … OFF
  3. EF Core: configure ValueGeneratedOnAdd

Detailed fix by platform

SQL

  1. sql
    SET IDENTITY_INSERT dbo.Orders ON;
    INSERT INTO dbo.Orders (Id, Total) VALUES (1001, 10);
    SET IDENTITY_INSERT dbo.Orders OFF;

How to diagnose

  1. Insert — Includes the identity column?
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

102 — SQL Server: Incorrect syntax near 'x'. (Msg 102) (SQL)10218456 — SQL Server: Login failed for user 'x'. (Error 18456) (SQL)18456207 — SQL Server: Invalid column name 'x'. (Msg 207) (SQL)207208 — SQL Server: Invalid object name 'x'. (Msg 208) (SQL)208245 — SQL Server: Conversion failed when converting the varchar value 'x' to data type int. (Msg 245) (SQL)2452627 — SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627) (SQL)2627547 — SQL Server: The INSERT statement conflicted with the FOREIGN KEY constraint 'x'. (Msg 547) (SQL)5478115 — SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115) (SQL)8115544

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.