Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Lineage ID Errors when using XML source

Unanswered Lineage ID Errors when using XML source

  • Friday, November 30, 2012 12:43 AM
     
     
    Sign In to Vote
    0

    I have created a package with XML as source and loads data to SQL tables. When i change the source to other XML file I am getting lineage ID errors like input column "XYZ" (382) has lineage ID 14429 that was not previously used in the Data Flow task, and when i just open the container and map usingcolumn names in the restore invalid column references editor and click apply it works. I need to automate the process to load set of XML files and everytime opening the container and manually fixing is not feasible.If some one can provide with a workable solution, it wold be really helpful.

    Thanks

     

All Replies

  • Friday, November 30, 2012 1:30 AM
     
     
    Sign In to Vote
    0
    Sounds like you are using XML files which do not have the same format.  Are you providing an xsd or just relying on the driver to automatically assume the structure of the file?  If you are using files with optional values then you need to make sure to provide an all inclusive xsd to have any prayer of it working.

    Chuck Pedretti | Magenic – North Region | magenic.com

     
  • Friday, November 30, 2012 3:01 AM
     
     
    Sign In to Vote
    0

    are you using any more transformations...? conversions..? did you check in advanced editor input column "XYZ" (382) has lineage ID 14429  I believe The metadata for the "XML" source has been  changed.  edit XMLsource and check the column mappings. You may get warnings on any transformations in the downstream pipeline. you need to edit the transformations and correct them. It will prompt you to automattically fix them

    Please mark as helpful and propose as answer if you find this as correct!!! Thanks,Miss Never Giveup .

     
  • Friday, November 30, 2012 4:50 AM
     
     
    Sign In to Vote
    0
    Hi Chuck, All the xml files have the same xsd file , it's only the xml file which is different and all the xml files have the same format.

    tmpradeep

     
  • Friday, November 30, 2012 4:54 AM
     
     
    Sign In to Vote
    0

    please check data tyoe of column XYZ at detination

    Please mark as helpful and propose as answer if you find this as correct!!! Thanks,Miss Never Giveup .

     
  • Friday, November 30, 2012 5:03 AM
     
     
    Sign In to Vote
    0

    Hi Dia,

    I am not using any transformations or conversions in package, it's a direct load from xml source to destination table.when I change the source the destination container drops the connection and when I click the container the restore invalid columns editor opens up, I click ok with map using column names option and the error gets fixed.

    tmpradeep

     
  • Friday, December 07, 2012 5:04 PM
     
     
    Sign In to Vote
    0

    I noticed that this has been marked as an answer. However this model (answer) does not seem to be scalable. I am running into exact same issue. If I were to automate this in Production via a Job to pick a different xml on each run, then it is not feasible. What is the automated solution other than manually click on with "Map using column name"

    Thanks In Advance!

     
  • Saturday, December 08, 2012 5:49 PM
     
     
    Sign In to Vote
    0

    Hi,

    I tried passing the xml file name through a variable and its working.

    using a for each loop to pass through variable picks up individual xml files and loads it, the connections are not dropping in this case and the package runs successful.

    tmpradeep