SQL entries with duplicate primary keys

Posted on 2008-06-22
Last Modified: 2010-04-21
The SQL database I'm working with is behaving strangely. There are a couple of issues, but the main one I want to ask about is what appears to be duplicate entries. I have two tables, order_items and riders. The primary key for the order_items is porder_item, and it is meant to be unique. When I query the database for results from order_items for a particular porder_item, I get one result. When I query for results from order_items inner joined with riders, I get two results, with the same porder_item. The new result row appears to be taken in part from a row that has a different porder_item value when querying the order_items table alone. I've checked my code, and porder_item is never explicitly set, just auto incremented. My first question is: Is this more likely to mean that the data is being inserted incorrectly somehow, or that it's OK but being retrieved incorrectly? My second question is: is this a symptom of a larger problem with the database, or is it more likely to be a code error somewhere?
Question by:bucky42
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
  • 5
  • 2
  • 2
LVL 11

Expert Comment

ID: 21842344
the results of the joined query are normal IF you have two rows in riders that have the same porder_item value (or are linked to the same row that contains that porder_item value)

Given that the results are correct for the database (that does not mean you are getting what you WANT - but that you are getting what you are asking SQL for) - I don't believe its an indication of anything wrong with your database.

Expert Comment

ID: 21842368
>>My first question is: Is this more likely to mean that the data is being inserted incorrectly somehow, or that it's OK but being retrieved incorrectly?<<

Most likely your JOIN is causing the dup.

The following should confirm if you have duplicate Primary Keys on porder_item.  If you see anything other than 1 for xcnt, then you have duplicate porder_item keys.

SELECT porder_item., count(*) as xcnt from dbo.d
GROUP BY porder_item.

Author Comment

ID: 21842546
The query above returns 1, so it appears that there isn't a dup in the database. But how can an inner join produce a dup result?

If this is my query

SELECT * FROM Rider r INNER JOIN Order_Item o ON r.fk_category=o.fk_category WHERE o.porder_item=XXXX;

where does that extra result come from?

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

LVL 11

Accepted Solution

CMYScott earned 500 total points
ID: 21842625
your join is going to bring back all combinations of rows where Rider.fk_category and Order_Item.fk_category have the same value.

so if you have one row in Order where fk_category has a value of 1000
but you have 2 rows in Rider where where fk_category has a value of 1000

the inner join is going to return
-- the combination of the single-row result in Order with the FIRST row-result in Rider
 -- the combination of the single-row result in Order with the SECOND row-result in Rider


Expert Comment

ID: 21842697
CMYScoot is on it.

You can determine which rows in by changing the above query a little.

BTW, if you have not guessed, I use the query below exactly for the purpose of figuring out why I have dup rows in a join when there are not "supposed" to be any dups. (And thanks for catching my copy & paster error in the earlier version).

SELECT fk_category., count(*) as xcnt from Rider
GROUP BY fk_categorym.

Author Comment

ID: 21842752
Aaah, so I need to join on a column which is unique for both tables to get a unique result. That makes sense.

Author Comment

ID: 21842827
or where the WHERE clause eliminates any unwanted rows; so there must be a WHERE clause acting on any column of a table that has multiple values for something being joined on.

Author Comment

ID: 21842840
No, scratch that last part. The WHERE clause has to be on something OTHER than the column with multiple rows in the join, since obviously all those rows would satisfy the WHERE clause if it were on them.

Author Closing Comment

ID: 31469588
Thanks! This revealed a major flaw in my understanding of inner joins.

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Sql Data via Excel--performance issues 2 57
SQL Merige returns error code when updating 15 57
Stored Procedure needs owner to execute 5 44
by Mark Wills PIVOT is a great facility and solves many an EAV (Entity - Attribute - Value) type transformation where we need the information held as data within a column to become columns in their own right. Now, in some cases that is relatively…
Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit If you want to manage em…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question