October 1, 2017 at 9:52 pm
| 0down votefavorite | I have an interesting problem with my custom ssis transformation component. The component worked very well on SQL Server 2008 but the company upgraded the server to 2014. The situation is the following, my component is a simple lookup, search id in a database and if it found add the id to the output if not add an error message, I think it is very simple. The source component which is connecting to this lookup component is totally dynamic, read the source file and add the columns to the output. The lookup component works very well in the first run, but if change the source file which contains different columns start to not work, the transformation component output remain the old columns list. I don't know why 🙁 I tried to call the ReinitializeMetaData function, it not helped. Sometimes I get this error, in this case the BusDate is an old column and of course it is not in the new column list.. [SSIS.Pipeline] Error: SP +S Lookup Component.Inputs[Input].Columns[BusDate] has lineage ID 13 that was not previously used in the Data Flow task. [SSIS.Pipeline] Error: "SP +S Lookup Component" failed validation and returned validation status "VS_NEEDSNEWMETADATA". When I debugged the code, I see the good values in the buffer, but not in the InputColumnCollection Please help me because I am totally puzzled, I don't know how can I solve this problem. Something is changed in 2014 what is can affect this? |
October 2, 2017 at 6:38 am
richardgaspar79 - Sunday, October 1, 2017 9:52 PM
0down votefavorite I have an interesting problem with my custom ssis transformation component. The component worked very well on SQL Server 2008 but the company upgraded the server to 2014. The situation is the following, my component is a simple lookup, search id in a database and if it found add the id to the output if not add an error message, I think it is very simple.
The source component which is connecting to this lookup component is totally dynamic, read the source file and add the columns to the output. The lookup component works very well in the first run, but if change the source file which contains different columns start to not work, the transformation component output remain the old columns list.
I don't know why 🙁 I tried to call the ReinitializeMetaData function, it not helped. Sometimes I get this error, in this case the BusDate is an old column and of course it is not in the new column list..
[SSIS.Pipeline] Error: SP +S Lookup Component.Inputs[Input].Columns[BusDate] has lineage ID 13 that was not previously used in the Data Flow task. [SSIS.Pipeline] Error: "SP +S Lookup Component" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
When I debugged the code, I see the good values in the buffer, but not in the InputColumnCollection
Please help me because I am totally puzzled, I don't know how can I solve this problem. Something is changed in 2014 what is can affect this?
It's rather difficult for anyone other than you to see what you are referring to and understand what you mean when we have neither your data nor your package to work with. However, that said, dynamic column names are potentially problematic with SSIS, and the 2014 version of it is even more so, and thus, it may just be that you were "getting away with it", and no longer can. There are ways to get around that kind of problem, but it often involves completely rethinking the methodology of the project. If you could post the package and some sample table create and insert statements for the tables it touches, we would have a reasonable shot at coming up with a solution.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply