Multiple Ways to Remove Duplicates from SQL Tables


This article discusses two different approaches available to remove duplicate rows from SQL table(s) which often becomes difficult over time as data grows if this is not done on time.

The presence of duplicate rows is a common issue that SQL developers and testers face from time to time, however, these duplicate rows do fall into a number of different categories that we are going to discuss in this article.

This article focuses on a specific scenario, when data inserted into a database table, leads to the introduction of duplicate records and then we will take a closer look at methods for removing duplicates and finally remove the duplicates using these methods.

Preparing Sample Data

Before we start exploring the different options available to remove duplicates, it is worthwhile at this point to set up a sample database which will help us to understand the situations when duplicate data makes its way into the system and the approaches to be used to eradicate it.

Set up Sample Database (UniversityV2)

Start by creating a very simple database which consists of only a Student table at the beginning.

Populate Student Table

Let us only add two records to the Student table:

Data Check

View the table which contains two distinct records at the moment:

Remove Duplicates from SQL Tables

You have successfully prepared the sample data by setting up a database with one table and two distinct (different) records.

We are going to discuss now some potential scenarios in which duplicates were introduced and deleted starting from simple to slightly complex situations.

Case 01: Adding and Removing Duplicates

Now we are going to introduce duplicate row(s) in the Student table.


In this case, a table is said to have duplicate records if a student’s Name, Course, Marks, and ExamDate coincide in more than one records even if the Student’s ID is different.

So, we assume that no two students can have the same name, course, marks and exam date.

Adding Duplicate Data for Student Asif

Let us deliberately insert a duplicate record for Student: Asif to the Student table as follows:

View Duplicate Student Data

View the Student table to see duplicate records:

Remove Duplicates from SQL Tables

Finding Duplicates by Self-referencing Method

What if there are thousands of records in this table, then viewing the table won’t be much help.

In the self-referencing method, we take two references to the same table and join them using column-by-column mapping with the exception of the ID which is made less than or greater than the other.

Let us look at the self-referencing method to find duplicates which looks like this:

The output of the above script shows us only the duplicate records:

Remove Duplicates from SQL Tables

Finding Duplicates by Self-referencing Method-2

Another way to find duplicates using self-referencing is to use INNER JOIN as follows:

Remove Duplicates from SQL Tables

Removing Duplicates by Self-referencing Method

We can remove the duplicates using the same method we used to find duplicates with the exception of using DELETE in line with its syntax as follows:

Data Check after Duplicates Removal

Let us quickly check the records after we have removed the duplicates:

Remove Duplicates from SQL Tables

Creating Duplicates View and RemoveDuplicates Stored Procedure

Now that we know our scripts can successfully find and remove duplicate rows, it is better to turn them into view and stored procedure for ease of use:

Adding and Viewing Multiple Duplicate Records

Let us now add four more records to the Student table and all the records are duplicates in such a way that they have the same name, course, marks and exam date:

Remove Duplicates from SQL Tables

Removing Duplicates by using UspRemoveDuplicates Procedure

Data Check after Removal of Multiple Duplicates

Multiple duplicates removed

Case 02: Adding and Removing Duplicates with Same IDs

So far, we have identified duplicate records having distinct IDs but what if the IDs are the same.

For example, think of the scenario in which a table has been recently imported from a text or Excel file that has no primary key.


In this case, a table is said to have duplicate records if all the column values are exactly the same including some ID column and the primary key is missing which made it easier to enter the duplicate records.

Create Course Table without Primary Key

In order to reproduce the scenario in which duplicate records in the absence of a primary key fall into a table, let us first create a new Course table without any primary key in the University2 database as follows:

Populate Course Table

Data Check

View the Course table:

Remove Duplicates from SQL Tables

Adding Duplicate Data in Course Table

Now insert duplicates into the Course table:

View Duplicate Course Data

Select all the columns to view the table:

Remove Duplicates from SQL Tables

Finding Duplicates by Aggregate Method

We can find exact duplicates by using the aggregate method by grouping all the columns with a total of more than one after selecting all the columns along with counting all the rows using the aggregate count(*)function:

This can be applied as follows:

Finding duplicates using aggregates method

Removing Duplicates by Aggregate Method

Let us remove the duplicates using the Aggregate Method as follows:

Data Check

USE UniversityV2

Remove Duplicates from SQL Tables

So, we have successfully learned how to remove duplicates from a database table using two different methods based on two different scenarios.

Things to Do

You can now easily identify and relieve a database table from duplicate value.

1. Try creating the UspRemoveDuplicatesByAggregate stored procedure based on the method mentioned above and remove duplicates by calling the stored procedure

2. Try modifying the stored procedure created above (UspRemoveDuplicatesByAggregates) and implement Clean up tips mentioned in this article.

3. Can you be sure that the UspRemoveDuplicatesByAggregate stored procedure can be executed as many times as possible, even after removing the duplicates, to show that the procedure remains consistent in the first place?

4. Please refer to my previous article Jump to Start Test-Driven Database Development (TDDD) – Part 1 and try inserting duplicates into the SQLDevBlog database tables, after that try removing the duplicates using both of the methods mentioned in this tip.

5. Please try to create another sample database EmployeesSample referring to my previous article Art of Isolating Dependencies and Data in Database Unit Testing and insert duplicates into the tables and try removing them using both of the methods you learned from this tip.


Useful tool:

dbForge Data Compare for SQL Server – powerful SQL comparison tool capable of working with big data.

Haroon Ashraf

Haroon's deep interest in logic and reasoning at an early age of his academic career paved his path to become a data professional.

He began his professional life as a computer programmer more than 10 years ago working on his first data venture to migrate and rewrite a public sector database driven examination system from IBM AS400 (DB2) to SQL Server 2000 using VB 6.0 and Classic ASP along with developing reports and archiving many years of data.

His work and interest revolves around Database-Centric Architectures and his expertise include database and reports design, development, testing, implementation and migration along with Database Life Cycle Management (DLM).
Haroon Ashraf