Question

I have two lookup transformations in my package. The first one executes fine though. The second one is a trouble maker.

I am having an error ‘Row yielded no match’, in the 2nd lookup while loading the final table in my database. It does not reoccur in the same rows every run. That is it gives me a different number of error result rows every run. Even when everything is exactly (input data, process...) the same through 2 different runs.

I re-directed the rows and checked for case- sensitivity and leading and trailing spaces, they were all ok, but the error still exists.

I checked (the redirected rows) manually for match (random 10 out of list), match exists, but SSIS still throws the same error.

I tried using all the three caching options (Full/Partial/No Cache) but in vain, the same error still appears.

I am not sure why this happens. It is driving me crazy, I am at a lost for thinking. Can you please help me know how I can fix this? Did any of you encounter such an error while doing the earlier SSIS executions?

Answer 1

我对你的眼光处理情况并不十分肯定,但这一增长问题是由于我们正在像处理一样建立起来的财产。

我们正在如何处理不匹配的记录,即没有相应的产出或拿到缺省记录。
Properties on the component when the no matching records i.e. fail the package when no match or parent package.

感谢

页: 1

友情链接