SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627)
An insert duplicated a primary key or unique constraint value.
Exact message you may see
Violation of PRIMARY KEY constraintViolation of UNIQUE KEY constraintCannot insert duplicate key in object
Seen on:
SQL
Meaning
2627 is for constraints; 2601 is the same thing for unique indexes. The message includes the duplicate key value.
Common causes
- Duplicate key value
- Re-inserting seed data
- Identity reseeded below existing values
⚡ Quick fix
- Use MERGE or check existence before insert
- Handle the error as "already exists"
- Reseed identity correctly (DBCC CHECKIDENT)
Detailed fix by platform
SQL
DBCC CHECKIDENT ('dbo.Orders', RESEED);
How to diagnose
- Key — Duplicate value shown?
- Identity — Reseeded?
🔧 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 14 Oct 2026