Hi,
I have developed a SSIS package on my desktop and the package involves loading of XML data into a database. The XML does not have inline schema and I generated the XSD file from SSIS.
I used Derived Column and Data Conversion to load the data into the database.
Now, i want to migrate the package to a server. Now, when i change the path of the XML and XSD files, all the tasks show error such as
"Input column 'Last_Updated' (4433) has lineage id 3586 that was not previously used in data flow...."
Why is this so? I am using the same XML/XSD files after i moved to the server.
Please advice a fix for this?
Regards,
Vikram
I was looking into this and i think i understand why this is happenning:
When we actually select a XML/XSD file, for every column which flows throught he data flow, SSIS assigns it a Lineage ID which is Unique and this Lineage ID is used internally.
When i change the XML/XSD file location, SSIS is assigning new Lineage ID's for the columns in the XML file.
The Data Flow tasks down of the XML source still try to look for the Lineage ID which was generated while the tasks were created.
As the Lineage ID's changed, they thrown error such as "Input column 'Last_Updated' (4433) has lineage id 3586 that was not previously used in data flow....". Here, 3586 is the Lineage ID which was created initially.
I am not sure how to avoid this error but once this error occurs, we have the open the immediate task after the XML source and fix it.
If anyone has an idea how to avoid this (This might help in large packages during migrations), please enlighten us.
Regards,
Vikram
