Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

LineageID of an input column has an another value in runtime

$
0
0

Hi all,

I upgraded my own data flow transformation component to SQL 2012. My component has one input and one asynchronous output.

I found the following unexplained behavior: a value of the LineageID of an input column at the runtime differs from a value which is currently set (and I can check it in designtime using Advanced Editor). E.g. component's input has only one column with the name "Address" and its LineageID equals 10. But during debugging component at the runtime I see that input contains only one column with the name "Address" but its LineageID equals 11. How is it possible?

So somebody could explain me what is it or give me an advice how to avoid this behavior. And in general how is it possible at all that LineageID for the same column has different values in the design time and the runtime?

PS. Versions of this component for SQL 2005 and 2008 work without such problem.

Igor


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>