I am having 34 columns in the source and destination table, i want to
move all the data to the destination table in single transformation by
SSIS. I dont want map each column in the source and destination (ie; 34
lines). I am trying to map this in the

Dataflow tab-->OLEDB Destination --> Mappings tab.

I want to combine all the columns in the source and pass the value to
the destination in single line (Not 34 lines) as we can do it in
SQLServer 2000.

Please post your answers if you have idea on this.

*** Sent via Developersdex http://www.developersdex.com ***

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote:

So you want to put 34 field from the source into ONE field in the destination?

Or will there be a one-to-one match from source to destination? In this
case, you need to map each and every field in the Mappings tab. Here's a
hint, though: when you FIRST create the OLE DB Destination, it will try to
map matching field names automatically.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Ahamed Faridh" wrote: