views:

27

answers:

2

I'm doing a fuzzy lookup on a view of a table which does a fine job returning similarities with the occasional exception, and I can't seem to figure out what is causing the problem. Every so often, the comparison will come up with null values from the lookup view, even though the values exist in both the view and the original table and the columns I have selected for "exact" match have identical values in both the lookup view and the source SQL.

Any thoughts as to why it's pulling null values?

alt text

A: 

Change your MinSimilarity threshold in the advanced settings - See this article

UndertheFold
+1  A: 

I discovered that by changing the order of the columns, and placing the exact matches at the top of the list, the null results were returned properly.

Scott K.