Skip to main content

DIFFERENCE IN USING ROW_NUMBER AND RANK ( )


When I wanted to know how to remove duplicates or in more sense, If i wanted to get Unique records, I went through a post which suggested to go for Rank function to find unique records. 
Well some suggested to for Row_number function. Here is a example where I worked on both the types and let you the differences.

CREATE TABLE Table1 (ID INT, employee VARCHAR(100), sal INT, dept VARCHAR(100))
GO
INSERT INTO Table1

SELECT 1, 'dhinakaran', 100, 'finance'
UNION ALL
SELECT 2, 'bharath', 100, 'marketing'
UNION ALL
SELECT 3, 'job', 100, 'accounts'
UNION ALL
SELECT 4, 'job', 100, 'markting'
UNION ALL
SELECT 5, 'job', 200, 'infrastruture'
UNION ALL
SELECT 6, 'raghu', 300, 'markting'
UNION ALL
SELECT 7, 'raghu', 400, 'finance'
GO
SELECT employee, sal, dept
FROM Table1
GO







we can observe that Employee JOB varies in dept and we can see salary.
Select the data without duplicate records as well select the data with maximum Sal.


By using Rank ( ) Function, If we try, by following query, we will get Following result.

select employee, sal, dept from  (select employee, sal, dept, rank () over
 (partition by employee order by sal desc) Rank from table1 ) a where Rank=1


 The same result will be obtained even If we try using ROW_NUMBER ( ). The snippet is shown Below.




 The real Difference between ROW_NUMBER and RANK ( ) function will come When I insert a data of similar Type.

For example, Let me insert one more value:
insert INto table1 values(8,'Job',200,'infrastruture')
 select * from table1
 go
Now For this table, If I use, RANK ( ) function, Then result is not we are expecting it. It is perfectly obtained by Using ROW_NUMBER ( ) only.

Result of both Snippets is as follows:




















Labels:

Comments

Post a Comment

Popular posts from this blog

BIG Data, Hadoop – Chapter 2 - Data Life Cycle

Data Life Cycle The data life cycle is pictorial defined as show below:     As we see, in our current system, we capture/ Extract our data, then we store it and later we process for reporting and analytics. But in case of big data, the problem lies in storing and then processing it faster. Hence Hadoop takes this portion, where it stores the data in effective format (Hadoop distributed File System) and also process using its engine (Map Reduce Engine). Since Map Reduce engine or Hadoop engine need data on HDFS format to process, We have favorable tools available in market to do this operation. As an example, Scoop is a tool which converts RDBMS to HDFS. Likewise we have SAP BOD to convert sap system data to HDFS.
73 comments
Read more

SSIS: The Value Was Too Large To Fit In The Output Column

I had a SSIS package where I was calling a stored procedure in OLEDB Source and it was returning a “The Value Was Too Large to Fit in the Output Column” error. Well, My Datatype in OLEDB source was matching with my OLEDB Destination table. However, when I googled, we got solutions like to increase the output of OLEDB Source using Advanced Editor option . I was not at all comfortable with their solution as my source, destination and my intermediate transformation all are having same length and data type and I don’t want to change. Then I found that I was missing SET NOCOUNT ON option was missing in Stored Procedure. Once I added it, my data flow task ran successfully. 
1 comment
Read more

How to Copy or Move Multiple Files from One Folder to Another Folder using Talend

Hello all, In this Post, I will explain how to move Multiple Files from One Folder (Say Source) to Other folder (Say Destination). This Post will also helps you to understand How to Declare Variable and Use it. To Declare a variable, We are go to use Contexts option in repository. Lets say we have two .txt files in Path D:/Source/ . My Requirement is to move the files from Source Folder ( D:/Source/ ) to Destination Folder ( D:/Dest/ ). Step 1: Open a New job Step 2: Now right click and Create a New Contexts from Repository. Give some Name and give Next. Step 3: Now Fill in the Source Directory Details where the loop on files should happen as shown in the snippet and give finish. Step 4: Now Context is created and The values will be changing based on each file in Folder. Step 5: Click and Drag the context from Repository to Context Job Window below the Job Designer. Step 6: If we Expand the Contexts, We can find the variable SourcePath is holdi...
10 comments
Read more