chaseurpuli (12/19/2013)
Phil Parkin (12/19/2013)
chaseurpuli (12/18/2013)
Phil Parkin (12/18/2013)
Phil Parkin (12/18/2013)
Sounds like you need an asynchronous script component.But why do you care what the column name is?
Thanks for your reply Phil. Unfortunately, the destination table is designed such that the column names should be combination of the names from Row 3 and Row 4.
You could map a source column called 'chicken' to a destination column called 'squirrel' with no issues at all: column names do not have to match.
Yes, we can match the source column to whatever destination column, but how do I define the destination column name as an expression (concatenation of two row values)?
I don't understand.
Why 'define' the destination column? Surely it already exists? Just map column x to it and forget about this concatenation malarkey.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin