 |
 |
Archives of the TeradataForum
Message Posted: Thu, 05 Aug 2010 @ 12:30:00 GMT
| Subj: | | Re: Effort Estimates for Data Loading |
| |
| From: | | Geoffrey Rommel |
| | 1. Load data from Teradata tables to another Teradata database. Is BTEQ the preferred method? | |
I assume you mean another database on the same system (same instance). In that case, the preferred method is insert/select, which can be done
through BTEQ, SQL Assistant, or any other tool that allows you to run SQL.
Loading data to a different Teradata instance is a more advanced topic. That can be done through FastExport from system A and FastLoad to
system B, TPT, or arcmain.
| | 2. Load data from third party sources to Teradata database. Can we use BTEQ combined with FLoad/Mload utilities or using a
traditional ETL tool would be more efficient? | |
If efficiency is your main concern, the best way is to export the data to flat files, preferably with "internal" formats -- 32-bit integers,
64-bit floats, varchar fields preceded by 16-bit lengths, etc. -- followed by loading with Fload or Mload. Usually, however, people are more
concerned about clarity and maintainability than sheer speed. An ETL tool is fine ... just keep it simple. :-)
> How does Teradata perform Audit, Balance and Controls for the above?
The utilities provide record counts and error counts in the logs, but anything beyond that must be programmed.
| |
