Today, while working on a new ETL in SSIS 2008 (using an old ETL as a model) I stumbled upon an error that was pretty new to me: Error at Data Flow Task [DTS.Pipeline]: input column "Column1" (1234) has lineage ID 1234 that was not previously used in the Data Flow task.
First of all, what is this lineage id?
According to TechNet Lineage id is "a property of the component or transformation used in the data flow task. It contains an integer value that will work as buffer pointer. Each column in the data flow task will be assigned a lineage id."
In fact, a column can have more than one lineage ID, if more transformations are applied on it.
Basically every column has an Id pointing to the buffer.
The fix to the problem was to refresh the mapping of the columns. The mapping was not refreshed, so basically a component is waiting for something at a buffer allocation identified by something that was not used before. Reading from the position 1234 in the buffer would yield nothing since no one is writing at that position before.
Tuesday, November 1, 2016
SSIS Errors
Posted by
Radu
at
7:56 AM
0
comments
Friday, January 14, 2011
Error in SSIS VS2005
Yesterday I had to put some code into SSIS packages.
Being a lazy person, what I usually do is copying one of the existing task ("Execute SQL Task") and changing the name and the code itself. Apparently after installing VS2005 SP1 this was not working anymore.
I had to create every "Execute SQL Task", set the connection, etc....which is not a lot but is slower than what I was used to.
The error message I was receiving while trying to copy was "An error occurred while objects were being copied. SSIS Designer could not serialize the SSIS runtime objects". A fast google search revealed this page and the easy fix by jaegd:
Register the xml parser dlls with the below commands.
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
It really worked and fixed my problem, but lets me wondering why Microsoft didn't fix it and release a SP2 with all this fixes.
Posted by
Radu
at
1:10 AM
0
comments
Labels: SSIS, VisualStudio