July 28, 2014 at 4:20 am
Hi,
I'm working on the conversion of a group of DTS to SSIS and the function of a part of them is to export data from an Oracle database to a Sql Server database using :
Source Oledb connection for ODBC
Destination Oledb provider for Sql Server
Transform Data Task
The migration is generating an Execute DTS 2000 package task that refers to a task of the original DTS (see attachment).
I really can't understand why this simple task is not being converted to a Data Flow task.
Thanks.
Alex.
July 28, 2014 at 5:06 am
alezar (7/28/2014)
Hi,I'm working on the conversion of a group of DTS to SSIS and the function of a part of them is to export data from an Oracle database to a Sql Server database using :
Source Oledb connection for ODBC
Destination Oledb provider for Sql Server
Transform Data Task
The migration is generating an Execute DTS 2000 package task that refers to a task of the original DTS (see attachment).
I really can't understand why this simple task is not being converted to a Data Flow task.
Thanks.
Alex.
The mapping between the functionality offered by the DTS datapump task and SSIS's data flow task is not a clean one. Some things can be done in the DTS datapump that cannot be done in a data flow task (they are probably done differently in SSIS).
So I think they decided that data pumps were too hard for the wizard to handle.
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply