I'm trying to setup a large number of imports from Oracle to SQLServer, and have come across a couple of slightly confusing usability issues.
Obviously I have to setup one export and one import for each table.
Setting up an export is no problem, but in order to setup the import I have to have a text file (or other intermediary structure) that I can use to map the import fields.
This is fine so long as I've run the export task to create a text file, but this appears to require setting up a Package, and setting properties in here to specify the export filename.
This whole process seems extremely unwieldy and adds enormous complexity to the task of setting up simple 'transfer from A to B' tasks.
Am I missing something here, or is it really this complex? The option to export immediately to a text file from the export editor would at least simplify this process, and a 'wizard' to automatically generate the pair of matched files (export/import) and auto-create a Package to run the task would make the process enormously simpler.
I'm looking at using VIEnt to simplify the import process over using something like SSIS, but it really does seem to need a few usability changes.
Can you outline the process you would typically go through to setup an import from (for example) Oracle to SQL Server?
Thanks,
Jason