Is there an easier way to define output columns for a script transformation?

• Pete T-366679

  SSCrazy

  Points: 2065

  More actions

  October 27, 2009 at 7:12 am

  #212982

  I have a script transformation component that I'm defining output columns for the output; my destination table has something like 200+ columns, lots of it just incremental repeating (name1, name2, etc...)

  Is there any other way I can define all of the outputs without having to click Add Column, click to rename it, click to change the datatype, click to change the length, ad nauseum? Can I copy and paste lines in code or something? I looked at the codefile for the package, and found the location, but there's an incremental ID on the columns....can I just copy and paste and it would be OK? How else can I do this?

  Thanks!

• SinisterPenguin

  SSC Eights!

  Points: 898

  More actions

  October 27, 2009 at 9:26 am

  #1071284

  Perhaps use a derived column transform? - though that wil be pretty labourious as well I guess...

  Something I often do is "create" the columns in the original select statement (asumming a database source).

  e.g. SELECT CONVERT(varchar(50),NULL) AS name1,

  CONVERT(SMALLINT,NULL) AS intCol1

  I'm not sure if it's best practice but it does add columns with the name you want & the correct data type into the Workflow....