One requirement of a project I'm working on is that the value within a column of my source be truncated to 30 characters. The source column is currently a length of 50. The previous developer was selecting the column, then downstream, used a
derived column to substring the value into a new column. The data set within this package is quite large and I'm attempting to clean it up. The full 50 length value is never used (other than for the source of the 30 length derived column).
The question - is it good, bad, or indifferent practice to do this SUBSTRING from within the OLE DB Source SQL Command right up front, rather than passing the entire length down to a derived column? I would assume, although maybe not eloquent
possibly lending itself to more difficult debugging, it would cut down on the amount of data in the pipeline and negate the need for a derived column transformation entirely, which I assume would cut down on process time.
I realize both would work - just curious about best practice/performance impacts.
View Complete Post