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
- Omit the identity column from INSERT
- For migrations: SET IDENTITY_INSERT dbo.T ON … OFF
- EF Core: configure ValueGeneratedOnAdd
Detailed fix by platform
SQL
- 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
- Insert — Includes the identity column?
- 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:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 12 Oct 2026