Delete duplicate records from table in sql server


RDBMS database best design practice never suggests us to keep duplicate records in a table, and If we are working on database schema/table design, we must create the primary key for each. But, many scenarios arise where duplicate records may insert in table, suppose we are working on the Development Database, and data is loaded from different sources where duplicate rows are possible. When we process this data to another database server (PreProd/ Prod), the data should be clean. Therefore, we need to delete the duplicate data.

Here I am creating a duplicate records scenario for the employee table, use the below query.
CREATE TABLE TEMP_EMPLOYEE
(
empId INT IDENTITY(1,1),
FName VARCHAR(100),
LName VARCHAR(100),
Salary DECIMAL(18,2),
Country VARCHAR(100)
)
INSERT INTO TEMP_EMPLOYEE(FName,LName,Salary,Country)
VALUES ('Dilip','Singh',20000,'IND')
INSERT INTO TEMP_EMPLOYEE(FName,LName,Salary,Country)
VALUES ('Raj','Kumar',30000,'USA')
INSERT INTO TEMP_EMPLOYEE(FName,LName,Salary,Country)
VALUES ('Anil','Singh',25000,'AUS')
INSERT INTO TEMP_EMPLOYEE(FName,LName,Salary,Country)
VALUES ('Dilip','Singh',20000,'IND')
INSERT INTO TEMP_EMPLOYEE(FName,LName,Salary,Country)
VALUES ('Dilip','Singh',20000,'IND')
SELECT * FROM TEMP_EMPLOYEE

--Before the deleting duplicate records, you must check it exists in your table or not
--We can check duplicate records exist in the table using bellow query

SELECT FName,LName,Salary,Country FROM TEMP_EMPLOYEE
GROUP BY FNameLNameSalaryCountry HAVING COUNT(*)>1

-- To remove Duplicate records from the table you can use below query

DELETE FROM TEMP_EMPLOYEE WHERE empId NOT IN ( SELECT MAX(empId) FROM TEMP_EMPLOYEE GROUP BY FName,LName,Salary,Country )
--**Use above query, when you want to keep the latest record

--Otherwise you can use below query

DELETE FROM TEMP_EMPLOYEE WHERE empId NOT IN ( SELECT MIN(empId) FROM TEMP_EMPLOYEE GROUP BY FName,LName,Salary,Country )

-- you can remove duplicate records by using Common Table Expression query given below

;WITH CTE AS (
SELECT FName,LName,Salary,Country,ROW_NUMBER() OVER (PARTITION BY FName,LName,Salary,Country ORDER BY FName,LName,Salary,Country) AS [Rank] FROM TEMP_EMPLOYEE
)
DELETE FROM CTE WHERE [Rank]>1

SELECT * FROM TEMP_EMPLOYEE
DROP TABLE TEMP_EMPLOYEE

Lookup Transformation in SSIS



Lookup transformation is responsible to join columns to the data flow/data set, by accessing additional information in a related table based on values in common columns.

Problem : We have a table EMP which data are fetching by OLEDB Source, this table contains column FName, LName, Salary  and Country. In the flow we need to add column empAddress and empPhone of Employees which information are in EMPDETAILS table.

Solution : We would use Lookup Transformation. Now see below the use of lookup transformation..

Create table EMP(

Id int identity(1,1),

FName VARCHAR(50),

LName VARCHAR(50),

Salary DECIMAL(18,2),

Country VARCHAR(50)

)


insert into EMP (FName,LName,Salary,Country)

Values('Dilip','Singh',20000,'IND')

insert into EMP (FName,LName,Salary,Country)

Values('Viru','Verma',40000,'USA')

insert into EMP (FName,LName,Salary,Country)

Values('Anil','Singh',30000,'UK')

insert into EMP (FName,LName,Salary,Country)

Values('Raju','Shukla',25000,'IND')

insert into EMP (FName,LName,Salary,Country)

Values('Raj','Kushwaha',20000,'AUS')

insert into EMP (FName,LName,Salary,Country)

Values('Salim','Sekh',26000,'PAK')

insert into EMP (FName,LName,Salary,Country)

Values('Nirmit','Katihar',27000,'AUS')

insert into EMP (FName,LName,Salary,Country)

Values('Dilip','Singh',23000,'AUS')
select * from EMP

Create Table EMPDETAILS

(

Id int identity(1,2),

empId int not null,

empAddress varchar(200),

empPhone Varchar(20)

)

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (1,'Delhi','9015518898')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (2,'california','8898283856')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (3,'Bristol','8898283226')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (4,'Haryana','9073348898')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (5,'Kingston','8875647643')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (6,'Lahor','8876664646')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (7,'Lahor','8876664646')

Insert into EMPDETAILS(empId,empAddress,empPhone)

Values (18,'UP','9087765564')




First drag and drop an OLEDB Source and make connection manager then select EMP table (I hope you know about OLEDB Source) . In data set you will find only columns like FName, LName, Salary, Country now we have requirement additional information like Address and Phone which belongs to EMPDETAILS table. 

  




Now we will use Lookup Transformation to  add or join column from EMPDETAILS table on the basis of common column, In EMPDETAILS table empId is the foreign key of EMP it means empId is common between EMP and EMPDETAILS on this basis we can perform Lookup Transformation.

Drag and drop Lookup Transformation and add flow path from Oledb Source and edit it. It will look like below .



Here I will stop the example and start the explain about lookup


GENERAL


 
Full cache: Full Cache is responsible to generate and load the reference dataset into cache before the Lookup transformation is executed.

Partial cache: Partial Cache is responsible to generate the reference dataset during the execution of the Lookup transformation. Load the rows with matching entries in the reference dataset and the rows with no matching entries in the dataset into cache.

No cache: No cache is responsible to generate the reference dataset during the execution of the Lookup transformation. No data is loaded into cache.

Cache connection manager: Cache connection manager is responsible to configure the Lookup transformation to use a Cache connection manager. This option is available only if the Full cache option is selected.
OLE DB connection manager: OLEDB connection manager is responsible to configure the Lookup transformation to use an OLE DB connection manager.

Specify how to handle rows with no matching entries

Select an option for handling rows that do not match at least one entry in the reference data set.

When you select Redirect rows to no match output, the rows are redirected to a no match output and are not handled as errors. The Error option on the Error Output page of the Lookup Transformation Editor dialog box is not available.

When you select any other option in the Specify how to handle rows with no matching entries list box, the rows are handled as errors. The Error option on the Error Output page is available.


CONNECTION



OLE DB connection manager: Here you can select an existing OLE DB connection manager from the list, or create a new connection by clicking New.

Use a table or view : Here you can select table from the list or you can create new table or view on by clicking New.

Use Result of an SQL Query: By choosing this option you can browse to a pre-existing query, build a new query check query syntax and preview query result.

Build Query: Create the Transact-SQL statement to run by using Query Builder, a graphical tool that is used to create queries by browsing through data. It look like below.


   
Browse Query: Using this option you can browse pre-existing query.

Parse Query: This is responsible to check the syntax of the query

Preview: This is responsible to preview query result.

COLUMNS


Available Inputs Column: This columns are come through data flow from a connection source. The input columns and lookup column must have matching data types. Use a drag-and-drop operation to map available input columns to lookup columns. You can also map input columns to lookup columns using the keyboard, by highlighting a column in the Available Input Columns table, pressing the Application key, and then clicking Edit Mappings.

Available Lookup Columns: The lookup columns are those columns comes through reference table in which you want to lookup values that match the input column. Use a drag-and-drop operation to map available input columns to lookup columns. Use the check boxes to select lookup columns in the reference table on which to perform lookup operations.

Lookup Column: These columns comes when you select column from available lookup columns. The selections are reflected in the check box selections in the Available Lookup Columns table.

Lookup Operation:  Select option to perform operation on lookup column.

Output Alias: The selections are reflected in the check box selections in the Available Lookup Columns table.

ADVANCED




Note: This option available only for Partial and no cache.

Cache size (32-bit):  Adjust the cache size (in megabytes) for 32-bit computers. The default value is 5 megabytes.

Cache size (64-bit):  Adjust the cache size (in megabytes) for 64-bit computers. The default value is 5 megabytes.

Enable cache for rows with no matching entries:  Cache rows with no matching entries in the reference dataset.

Allocation from cache: Specify the percentage of the cache to allocate for rows with no matching entries in the reference dataset.
Modify the SQL statement:  Modify the SQL statement that is used to generate the reference dataset.

Error and Output : I will explain it latter in Error Handling..

Now I am starting output explanation..

Please apply Data viewers on every path, input data looks like below.

 
Here only on column match with column in reference table. for example id of EMP(input table) is matched with empId in EMPDETAILS(reference table).



 Here show matched output data, you can see empAddress and empPhone columns are join in dataset.

like this you can see not matched data as given below..



 







Related Posts

What is the Use of isNaN Function in JavaScript? A Comprehensive Explanation for Effective Input Validation

In the world of JavaScript, input validation is a critical aspect of ensuring that user-provided data is processed correctly. One indispensa...