Archives of the TeradataForum
Message Posted: Tue, 20 Jun 2006 @ 14:54:10 GMT
| Subj: | | Re: DB2 to teradata Data migration considerations |
| |
| From: | | Geoffrey Rommel |
| | Currently we have solution for data migration as unload DB2 tables and send it to temporary machine to hold data (we have restriction to
store on the same MVS machine where DB2 lies) then load to teradata using mload | |
| | Alternatively, we are thinking to use OLE DB access module for the same job. | |
I assume that this only has to be done once. If so, ease of use for you is more important than efficiency, so OLE DB is probably the way to go.
You have at least three more difficult options:
- An ETL tool such as DataStage or Informatica.
- Exhibit A in the white paper shows a prototype Cobol routine that can move data directly from DB2/MVS to Teradata without having
to use an intermediate file. As it is written now, you would have to hard-code the metadata (column names and data types) in the program, so you
would have to write a new program for each table you want to transfer. It sounds as if you are writing your own MultiLoad scripts for each table,
so maybe it would be just as easy to write the Cobol routines.
- Generalize the Cobol routine to use dynamic SQL and an SQLDA.
| 
