Click here to Skip to main content
15,887,746 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
What is logic behind the merge join in SSIS? In SQL server, we don't have to sort the sources before join. But why it is necessary in SSIS?
Posted

From MSDN Documentation: In Integration Services, the Merge and Merge Join transformations require sorted data for their inputs. The input data must be sorted physically, and sort options must be set on the outputs and the output columns in the source or in the upstream transformation. If the sort options indicate that the data is sorted, but the data is not actually sorted, the results of the merge or merge join operation are unpredictable.
When I read something like this my first impression is that I believe there must be a significant performance increase or a significant simplifying of complex logic happening under the hood. Not sure if that helps you, but if you want, I got the info here[^].
 
Share this answer
 
Hi,

Sql Server Merge is used to add new value or modify the existing value basing upon the conditions matches or not matches . It improves the performance of the database as it passes through data only once.


SSIS Merge and Merge Join:

Here we need to sort the data before we apply above transformations in the data flow tasks. Merge combines the data in row wise level where merge join combines the data in column wise level. If at all, when we use different oledb sources, excel sources and flat files and when we just want to combine the data as a single table (interms of columns) we go for merge join transformations. Where as when we want to combine the data in a row level.

Please excuse and rectify me if wrongly said.

Thanks,
Durga
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900