SSIS:MatchUp:Matchcodes:Swap Matching: Difference between revisions
Created page with "← SSIS Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; pa..." |
No edit summary |
||
| Line 86: | Line 86: | ||
[[File: | [[File:SSIS_MU_Matchcode_SwapMatch1.png|link=]] | ||
| Line 96: | Line 96: | ||
[[File: | [[File:SSIS_MU_Matchcode_SwapMatch2.png|link=]] | ||
| Line 102: | Line 102: | ||
[[File: | [[File:SSIS_MU_Matchcode_SwapMatch3.png|link=]] | ||
Revision as of 01:09, 21 November 2014
Swap matching is used to catch matches when two fields are flipped around. The most common occasion is catching the "John Smith" and "Smith John" records. But there are other uses:
Comparing Household Records
When there are two or three first or full names per record, a list provider may claim that every record is always "husband, wife, then children," but records will read wife then child and husband:
In the above example, select Either component can match for Swap Pairs A, B, and C
Comparing up to Three Address Lines
Although the address splitter works well in the US and Canada, some European countries can cause problems. A typical Euro-Matchcode will not use street split components and look at three address lines instead. The swap matching ensures that every address line is compared with every other address line.
Again, select Either component can match for Swap Pairs A, B, and C.
Don’t always discard the street split component matchcodes because you are working with a foreign database. Sometimes the street splitter will yield usable results. Therefore, a combination of approaches will often work.