SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Skip Header Rows in Excel and Concatenate Excel column names in SSIS


Skip Header Rows in Excel and Concatenate Excel column names in SSIS

Author
Message
Learning1
Learning1
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 94
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)?
Phil Parkin
Phil Parkin
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19544 Visits: 20462
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.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search