When using lookup transformation in SSIS, if you set "NoMatchBehavior" to "Treat rows with no matching entries as errors. ", this will cause the entire task to fail. If you set this attribute to" Send rows with no matching entries to the no match output. "This will not cause task failure.
Example:
[Lookup [1] Error: Row yielded no match during lookup.
[Lookup [1] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. the "component" Lookup "(1)" failed because error code 0xC020901E occurred, and the error row disposition on "output" Lookup Match Output "(3)" specifies failure on error. an error occurred
On the specified object of the specified component. There may be error messages posted before this with more information about the failure.
[SSIS. pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. the ProcessInput method on component "Lookup" (1) failed with error code 0xC0209029 while processing input "Lookup Input" (2 ). the identified component returned an error from the ProcessInput
Method. the error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. there may be error messages posted before this with more information about the failure.
In "Lookup Transformation Editor, setting "specify how to handle rows with no matching entries" to "redirect rows to no match output" is equivalent to setting "NoMatchBehavior" to "Send rows with no matching entries to the no match "output. "; if you set" specify how to handle rows with no matching entries "to" fail
Component ", which is equivalent to setting" NoMatchBehavior "to" Treat rows with no matching entries as errors. ", the entire task will be fail.