Re: data Extract, Transform, Load (ETL) on Iseries

[CRPence <CRPbottle@xxxxxxxxx>]

  If there is an "option for a complete refresh" to effect the 
representation of the "daily updates" at the target database, I would 
_consider_ using CREATE VIEW to define each of the target outputs; i.e. 
the joins, omitted columns, summaries, and other transformations.  Then 
export\transfer the data into those equivalent TABLE objects in the 
target database.  A script on the other database could /pull/ the data; 
for anything a VIEW could not as easily achieve, stored procedures might 
instead return the result sets.

Regards, Chuck

On 11 Jun 2012 08:35, Stone, Joel wrote:
> New project requires ETL to copy Iseries data to .NET for www
> inquiries.
> Can be daily updates (no requirement for real time).
> Can anyone suggest how to handle this?
>
> I have to get changed data to Biztalk, and also have the option for a
> complete refresh.
>
> There will be data manipulation, for example joining to other files,
> discarding unnecessary fields, etc.
>
> What is a good method?
> <<SNIP>>
> *   Any other methods I should look at?