Error: Row yielded no match during lookup.
I am getting this error while using Lookup transformation. pls help
November 17th, 2010 10:30am

It sounds if there is no match for the specific value in your Lookup. You can redirect this row to an ErrorOutput like Derived Column, paste a Default Value for that and use a Union Task to merge the data again.
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2010 10:55am

I am getting this error while using Lookup transformation. pls help What sort of help are you expecting? The error is self-explanatory - it means the lookup attempted to find a value in its lookup set and failed to find it. If you want more help than that then you'll have to provide more information. Help us to help you.http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me
November 17th, 2010 10:59am

Apology for not providing the details. The problem is I am using lookup transformation with 2 columns as lookup condition. Every time the Entire data set redirected to the error table (those lookups are valid lookup). I have checked the metadata at both the side and found OK(Numeric datatype). This problem occurring if FULL CACHE mode is selected. Working fine if NO CACHE mode is selected. Paritosh
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2010 5:17am

Apology for not providing the details. The problem is I am using lookup transformation with 2 columns as lookup condition. Every time the Entire data set redirected to the error table (those lookups are valid lookup). I have checked the metadata at both the side and found OK(Numeric datatype). This problem occurring if FULL CACHE mode is selected. Working fine if NO CACHE mode is selected. Paritosh OK. There are occasions where the FULL CACHE can behave differently to NO CACHE although the only scenario in which I can recall this happening is when the database has a case-insensitive collation. SSIS lookups using FULL CACHE are case-sensitive and hence can exhibit different behaviour to NO CACHE but this is only an issue when comparing strings. It shouldn't be an issue for Numeric datatypes. The point is - FULL CACHE is known to sometimes behave differently to NO CACHE but I can't provide much more help than that I'm afraid. @Jamiethttp://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me
November 18th, 2010 5:46am

Hi Paritosh, As you know, a lookup transfomation task should output match data and no match data. By default, the no match data will be handled as Fail. This will cause the error you mentioned to be promptted. To resolve the issue, please follow these steps: Double-click the Lookup transfomation you added to the package. Select "Ignore failure" or "Redirect rows to error output" or "Redirect rows to no match output" from the "Specify how to handle rows with no matching entries" For more information, please see: Lookup Transformation Editor (General Page): http://technet.microsoft.com/en-us/library/bb895370(SQL.100).aspx If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 2:04am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics