There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
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
-
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 today
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
Active today
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
Active today
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;
Active today
>> 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
The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
This shares a stored procedure to retrieve permissions for a given user on the current database or across all databases on a server.
During the weekend, I was asked to investigate into a deadlock in SQL Server 2014. SQL being something I don’t really fancy myself being an expert at, I had to do some refreshing. This article is a collection of my notes.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
Suggested Courses
Course of the Month4 days, 20 hours left to enroll
580 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.