We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Solved
Cannot update table (Violation of PRIMARY KEY constraint)
Posted on 2009-07-09
Hello i have two tables tblPollutants and Pollutant
When i am trying to run the query that exists in the code Snippet: i am getting this error:
Violation of PRIMARY KEY constraint 'PK_tblPollutants'. Cannot insert duplicate key in object 'dbo.tblPollutants'.
the query finds similar values between the two tables and updates the id from the Pollutant table
i have attached an sql script in order to create the two tables
When i am trying to run the query that exists in the code Snippet: i am getting this error:
Violation of PRIMARY KEY constraint 'PK_tblPollutants'. Cannot insert duplicate key in object 'dbo.tblPollutants'.
the query finds similar values between the two tables and updates the id from the Pollutant table
i have attached an sql script in order to create the two tables
This is the query where i am facing the problem
Update tblPollutants
set tblPollutants.PollutantID = Pollutant.PollutantId
FROM tblPollutants INNER JOIN
Pollutant ON tblPollutants.Pollutant = Pollutant.PollutantName
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
3
3- +1
11 Comments
If those are autonumbered primary key fields, they won't necessarily match between tables and you can't change one to match the other when the other table has a record with that id already existing hence your error message. The main point though is you shouldn't be. If these ids were to match in the first place, the design of the tables/database should be reviewed for possible change and use trigger, cascading keys, or handle inserts in order where you use the SCOPE_IDENTITY() of first insert for subsequent ones.
Active 6 days ago
You are trying to update the primary key column with a value thats already there that's why it is throwing the error
try this on the backup database
Update tblPollutants
set tblPollutants.PollutantID = Pollutant.PollutantId
FROM tblPollutants INNER JOIN
Pollutant ON tblPollutants.Pollutant = Pollutant.PollutantName
WHERE tblPollutants.PollutantID <> Pollutant.PollutantId
try this on the backup database
Update tblPollutants
set tblPollutants.PollutantID = Pollutant.PollutantId
FROM tblPollutants INNER JOIN
Pollutant ON tblPollutants.Pollutant = Pollutant.PollutantName
WHERE tblPollutants.PollutantID <> Pollutant.PollutantId
Your Pollutant ID 287, 310 are repeated twice and hence you obtain the error.
Fix it out in the INSERT statements to get it corrected.
Fix it out in the INSERT statements to get it corrected.
aneeshattingal: ti gives me the same error your query
Violation of PRIMARY KEY constraint 'PK_tblPollutants'. Cannot insert duplicate key in object 'dbo.tblPollutants'.
The statement has been terminated.
rrjegan17:
when i am running this query i see this values only once
select pollutantid from pollutant
where pollutantid in (287,310)
mwvisa1: i am joining them on nvarchar column tblPollutants.Pollutant = Pollutant.PollutantName
Violation of PRIMARY KEY constraint 'PK_tblPollutants'. Cannot insert duplicate key in object 'dbo.tblPollutants'.
The statement has been terminated.
rrjegan17:
when i am running this query i see this values only once
select pollutantid from pollutant
where pollutantid in (287,310)
mwvisa1: i am joining them on nvarchar column tblPollutants.Pollutant = Pollutant.PollutantName
If you see in the sample Inserts provided "Carbon tetrachloride" repeats twice in both the tables.
Kindly check that record and fix it.
Kindly check that record and fix it.
My point is that those tables primary keys don't have to match. If they are joined by Pollutant, you can just ensure that the value of that field and PollutantName are set as unique in each of tables. To have the numbers match, you would have to review design as stated as you probably don't want to insert these separately as currently doing as each table can assign different auto id based on transactions that occurred before.
rrjegan17: Thanks a lot how did you managed to find that? it seems to working right now let me check it on my main database and i will accept your answer
mwvisa1: Those tables primary keys have to match in my case because i just want to copy the values from table a to table b for for a data warehouseproject
mwvisa1: Those tables primary keys have to match in my case because i just want to copy the values from table a to table b for for a data warehouseproject
Then you could have just done this:
SELECT *
INTO b
FROM a;
Or:
-- with no auto increment on id column in b
DELETE FROM b;
INSERT INTO b
SELECT * FROM a;
SELECT *
INTO b
FROM a;
Or:
-- with no auto increment on id column in b
DELETE FROM b;
INSERT INTO b
SELECT * FROM a;
>> Thanks a lot how did you managed to find that? it seems to working right now let me check it on my main database and i will accept your answer
Just tried to find out the error record by running the insert scripts you provided in my machine.
And found what's wrong with the data since syntax is correct.
Just tried to find out the error record by running the insert scripts you provided in my machine.
And found what's wrong with the data since syntax is correct.
Featured Post
Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
In this article we will learn how to fix “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Suggested Courses
Course of the Month8 days, 15 hours left to enroll
734 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.