Fuzzy Lookup is not working in SSIS 2008

  • Hi All,

    I'm using SSIS 2008 , I have one simple package with Excel is the source, then will connects to the FuzzyLookUp transformation then the result from FuzzyLookUp connects to the OLEDB Destination.

    Here,when I execute the package, it shows the number of rows transfered from source to FuzzyLookUp, but after that it is not processing the records. 🙁

    I have tried this with different values of Similarity threshold (0.0 to .99) , I have source value like ( Production,Sales,..) and reference table has got values like (Product,Sales,..) , so there should be some matching results.

    Also when I run the package, command prompt just flashes and disappears. Also in the FuzzyLookUp I can see a warning as "Length of Input column is not matching with the length of the reference column"

    Can someone tell me why it is not working?

    Thanks & Regards,
    MC

  • Are there any errors?

    Does the fuzzy lookup component turn yellow in BIDS? (and does it stay yellow?)

    Or does it turn green or red?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Hi,

    There is no error ,it turned Yellow and continued as yellow.

    There is no output from Fuzzy Look Up and so the destination object didn't executed (didn't even turn to Yellow)

    I'm able to do the same example in SSIS 2005.!!!

    Thanks & Regards,
    MC

  • Let's first get rid of the warning. Make sure all the lenghts of the input columns match those of the reference columns.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Da Zero,

    I understood what is happening.

    Long back I had a trouble in using Excel Source/destination in SSIS 2008, then as a reply for my post in this forum I have done some change in the property of project solution, in the Configuration properties, in the Debugging section I have made the Run64BitRuntime = False then I was able to use Excel source/destination.

    Now for the fuzzyLookUp issue, when I tried with some OLEDB source,and when I made Run64BitRuntime = True , FuzzyLookUp worked!!!.

    So now the problem is

    1) If I make Run64BitRuntime = False then I can use Excel Source/destination , but FuzzyLookUp will not work.

    2) If I make Run64BitRuntime = True then I can't use Excel Source/destination , but FuzzyLookUp will work.

    Is this a bug in SSIS 2008? Or some settings problem from my side?

    I have attached the Configuration property setting screenshot.

    Thanks & Regards,
    MC

  • It could be an issue with SSIS:

    https://connect.microsoft.com/SQLServer/feedback/details/488387/fuzzy-lookup-triggers-sqldumper-even-with-very-small-dataset-with-run64bitruntime-set-to-false?wa=wsignin1.0

    If you google on "SSIS fuzzy lookup 64 bit", you get all sorts of posts of people complaining about fuzzy lookup and 64bit set to false.

    You need however 32-bit to run the JET driver needed for the Excel source (since JET doesn't work in 64bit).

    But it is a best practice to design your packages so that 32bit tasks are separated from 64bit tasks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Thanks Da-zero,

    So it is a bug, thanks for your information, and yes while creating the tasks we have to make 32 and 64 separate.

    By the way how do we know which are the 23 bit tasks and which are 64?

    Thanks & Regards,
    MC

  • The only tasks that I know of for the moment are tasks/components working with Excel.

    Put those into a package that uses 32-bit. For all the rest you can create a 64-bit package.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Ok.. Thanks.

    Thanks & Regards,
    MC

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply