SSIS : Output column with different datatype size

  • Dear All,

    I have an SSIS package that at some point does un union.

    All the columns from that union are str with size 3 but the output variable appears with size 50

    for example:

    SECURITY CURRENCY   (input1)          SECURITY CURRENCY (intput2)       SECURITY CURRENCY (Output)

    Both SECURITY CURRENCY inputs are size 3 but the outup is size 50.

    Can someone help?

    Thank you 

  • river1 - Thursday, September 28, 2017 4:37 AM

    Dear All,

    I have an SSIS package that at some point does un union.

    All the columns from that union are str with size 3 but the output variable appears with size 50

    for example:

    SECURITY CURRENCY   (input1)          SECURITY CURRENCY (intput2)       SECURITY CURRENCY (Output)

    Both SECURITY CURRENCY inputs are size 3 but the outup is size 50.

    Can someone help?

    Thank you 

    Help with what, exactly?

    • Understanding why the length is not 3?
    • Understanding how to change the length to 3?
    • Understanding why this is not necessary going to cause any errors?
    • something else?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • Hello,

    Thank you for your answer.

    I would like to understand how can I change it from 50 to 3 in order to not get this warning

  • river1 - Thursday, September 28, 2017 8:36 AM

    Hello,

    Thank you for your answer.

    I would like to understand how can I change it from 50 to 3 in order to not get this warning

    • Right click on the data source and 'Show Advanced Editor'.
    • Navigate to Input and Output Properties/OLEDB Source Output/Output Columns and select the column whose length needs to be changed
    • Change the length in the right-hand pane and save

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • I did it. Unfortunatelly it does not work

  • river1 - Thursday, September 28, 2017 9:52 AM

    I did it. Unfortunatelly it does not work

    OK. I'm guessing that you don't require any further help with this though, given the lack of detail you have provided.

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • Union all is holding on to metadata where you had one of the inputs defined differently, after getting both inputs to the same length delete the union all and pull another union all in.  This will grab the updated metadata.  There is no advanced editor for a union all.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply