June 23, 2008 at 1:40 am
Just in case there is some patch I don't know about, I'm using MS Visual Studio 2005, version 8.0.50727.42, SQL Server Integration Services Designer Version 9.00.2047.00
I have 3 lookup transformations on the same table, but each one for a different reason - to get lookup values for 3 different input columns. I've triple-checked: each of these columns in each of the row in the data flow has corresponding lookup value.
This is a good description of the problem but the solution does not work for me. I have disabled caching. Enable memory restriction is off. I tried deleting them and recreating them without copy-paste operations. I even tried to fool SSIS by placing a manual SQL select query instead of selecting table in each of the lookups but I get the same error: the dataflow is failing on the first lookup (with a wrong error no matching rows), although some following transformations are greened.
When I rewrote those SQL-s so that I use different aliases in the select for the tablename and different aliases for the resulting columns for each of the lookups, I don't receive that error anymore: I get a new error:
Error: 0xC020901E at Data Flow Task Povuci sve podatke o radnicima, Lookup općina stanovanja id [31802]: Row yielded no match during lookup.
Error: 0xC0209029 at Data Flow Task Povuci sve podatke o radnicima, Lookup općina stanovanja id [31802]: The "component "Lookup općina stanovanja id" (31802)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Output" (31804)" specifies failure on error. An error occurred on the specified object of the specified component.Error: 0xC0047022 at Data Flow Task Povuci sve podatke o radnicima, DTS.Pipeline: The ProcessInput method on component "Lookup općina stanovanja id" (31802) failed with error code 0xC0209029. 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.
Does anyone know the solution to this problem?
It's been crippling me for several days now!!
Thanks!!
June 23, 2008 at 5:37 am
Try creating another Connection Manager to the data source.
Set the "RetainSameConnection" property of the new connection manager to true.
Set the lookups you are having trouble with to this new connection manager.
Turn back on the full caching unless you had another reason to turn it off. Lookups with partial or no caching perform horribly. I would also suggest ordering the query for the lookup source by the lookup key values so the component has an easier time sorting the cache results.
July 15, 2008 at 8:21 pm
Champ ... got my error out of the way. I would like to add one more things which is check the data types
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply