The sort-merge join (also known as merge-join) is an example of a join algorithm and is used in the implementation of a relational database management system.
The basic problem of a join algorithm is to find, for each distinct value of the join attribute, the set of tuples in each relation which display that value. The key idea of the Sort-merge algorithm is to first sort the relations by the join attribute, so that interleaved linear scans will encounter these sets at the same time.
In practice, the most expensive part of performing a sort-merge join is arranging for both inputs to the algorithm to be presented in sorted order. This can be achieved via an explicit sort operation (often an external sort), or by taking advantage of a pre-existing ordering in one or both of the join relations. The latter condition can occur because an input to the join might be produced by an index scan of a tree-based index, another merge join, or some other plan operator that happens to produce output sorted on an appropriate key.
Let's say that we have two relations and and . fits in pages memory and fits in pages memory. So, in the worst case Sort-Merge Join will run in I/Os. In the case that and are not ordered the worst case time cost will contain additional terms of sorting time:, which equals (as linearithmic terms outweigh the linear terms, see Big O notation – Orders of common functions).
Read more about Sort-merge Join: Pseudocode, Simple C# Implementation
Famous quotes containing the word join:
“Each man, if he attempts to join himself to others, is on all sides cramped and diminished of his proportion; and the stricter the union, the smaller and the more pitiful he is. But leave him alone, to recognize in every hour and place the secret soul, he will go up and down doing the works of a true member, and, to the astonishment of all, the work will be done with concert, though no man spoke.”
—Ralph Waldo Emerson (1803–1882)