Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

Get Rid of the Duplicate Records

Posted on January 14, 2009May 10, 2011 by slowder

Time after time I’ll get a table that has duplicates in it and I have to clear out all the duplicate entries while leaving a distinct set of records. There’s a couple of ways to solve the problem. Today I want to take you through my standard fix.

  1. Script the source table out to a temporary table.
  2. INSERT the DISTINCT records into the temporary table.
  3. TRUNCATE the original table.
  4. INSERT the records back into the source table from the temporary table.

Let’s run through these steps in AdventureWorks.

First, we’re going to set up a table that will be filled with duplicate records.

CREATE TABLE dbo.Contact(
Title NVARCHAR(8)
, FirstName NVARCHAR(50)
, MiddleName NVARCHAR(50)
, LastName NVARCHAR(50)
, Suffix NVARCHAR(10)
)

Next, we’re going to fill that table with two copies of all contacts in our Person.Contact table.

INSERT INTO dbo.Contact
SELECT
Title, FirstName, MiddleName, LastName, Suffix
FROM Person.Contact
UNION ALL
SELECT
Title, FirstName, MiddleName, LastName, Suffix
FROM Person.Contact

OK, in case you’re not familiar with how to check for dupes, here’s a quick way to check. Select all the columns that should be DISTINCT, then GROUP by those columns, and add the HAVING COUNT(*) > 1 clause. This will show you any records that are duplicated in your table.

SELECT
Title, FirstName, MiddleName, LastName, Suffix
FROM dbo.Contact
GROUP BY
Title, FirstName, MiddleName, LastName, Suffix
HAVING COUNT(*) > 1

I’m showing 19,907 records have been duplicated. Your mileage may vary.

Now, let’s create our temp table. My table of choice is a table variable. No need to create a table that will last longer than this operation, and since this is a one shot deal, I’m not very worried about optimizing the operation with indexes or anything too fancy.

DECLARE @Contact TABLE (
Title NVARCHAR(8)
, FirstName NVARCHAR(50)
, MiddleName NVARCHAR(50)
, LastName NVARCHAR(50)
, Suffix NVARCHAR(10)
)

Now, we INSERT the DISTINCT records into our table variable.

INSERT INTO @Contact
SELECT DISTINCT
Title, FirstName, MiddleName, LastName, Suffix
FROM dbo.Contact

Then we TRUNCATE the source table.

TRUNCATE TABLE dbo.Contact

Now sometimes you’ll have to keep records online while removing the duplicates, in which case you’ll have to come up with a way to delete the records that you keep records “online” while doing this delete. There are some ways to do it… can you think of any?

Finally, we want to insert the records back into the table.

INSERT INTO dbo.Contact
SELECT
Title, FirstName, MiddleName, LastName, Suffix
FROM @contact

Double check to make sure you got all the duplicates cleared up.

SELECT
Title, FirstName, MiddleName, LastName, Suffix
FROM dbo.Contact
GROUP BY
Title, FirstName, MiddleName, LastName, Suffix
HAVING COUNT(*) > 1

And that’s how you get rid of duplicates. I’d highly suggest applying a DISTINCT constraint to the table. I’d also suggest you consider a PRIMARY KEY, that way if you need to remove duplicates, you could remove them by ID, which would help you out if you needed to deal with duplicates while leaving your records “online”.

If you have any questions, please feel free to reach out. I’m here to help!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme