Post reply

Data Cleansing mapping problem

  • April 18, 2007 at 5:31 am

    #153533

    I am just starting out with SSIS and trying to get the feel of data cleansing using it. But on my very first project for data cleansing I've got into this weird error.

    My data flow is very simple, it has a OLE DB source, Fuzzy Lookup and OLE DB destination. I've built three tables for this purpose, one is source, one is reference (it will be used to match for the real entries in fuzzy lookup) and the last is the destination table.

    In all the three tables I've a field of City which I'd like to Fuzzy lookup in the reference table and if it crosses certain confidence level, I'd like to insert to the destination table. City in all the tables has the same datatype, defined in the same way, it is varchar(50).

    But when in the fuzzy lookup I try to map the Source tables City field to reference tables City field, it gives me this error:

    The following columns cannot be mapped:

    [City, CityRef]

    One or more columns do not have supported data types, or their data types do not match.

    Although as I have mentioned before, both have same data types and are defined in the same manner (i.e. I've just selected the datatypes for those columns and all the other settings are left to default). I just cannot understand why this is happening, plz help me with this. FYI I've also tried to give the City Column different datatypes in all the tables like varchar(max), text, Only to be greeted with the same error message.

     

    Waiting for your reply!!

    Regards,

    Sajid.

  • April 26, 2007 at 10:17 am

    #702674

    I get the same error when i try using the regular lookup.

    There is something definetly wrong with SSIS.

    Both of my tables have the same datatypes.

     

    Alex S

  • July 4, 2008 at 3:51 am

    #838279

    hello,

    I've got the same error, but then I tried another provider, and then it works. First I've chosen the OLE native client ( or so) and it fails. Then I took the OLE Provider for SQL Server and it works.

    The columns are defined both nvarchar(200).

    best regards

    manfred

Viewing 3 posts - 1 through 2 (of 2 total)

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