2627 🗃️ SQL

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.

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

  1. Use MERGE or check existence before insert
  2. Handle the error as "already exists"
  3. Reseed identity correctly (DBCC CHECKIDENT)

Detailed fix by platform

SQL

  1. DBCC CHECKIDENT ('dbo.Orders', RESEED);

How to diagnose

  1. Key — Duplicate value shown?
  2. Identity — Reseeded?

🧠 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.