Re: ETL method - goodbye triggers, hello journals

But won't you run into problems if the same record changed twice in a
day? You are getting the record based on a key that changed the second
time. I would think you could run into issues with that.

Also, if the price record changes why would you need to send the
CONTRACT record? Don't know your data so probably don't know what I am
talking about.

On Tue, Jun 12, 2012 at 2:42 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

Why save off keys?

Example:

Price record is changed to $3.10, then to $3.50, then to $3.25

Since price changed, must send the current PRICE record and the associated CONTRACT record.

Want to only send once at EOD, so I save off the CONTRACT ID and then at EOD send CONTRACT and all its associated records such as the PRICE record.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Tuesday, June 12, 2012 3:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: ETL method - goodbye triggers, hello journals

Why save off the keys? You have the whole record coming in so you do
your transformation and write to table for transfer or just send it
over immediately?

One simple solution would be to transform the data and then call a
Stored Procedure to update you ETL data using JDBC.(Assuming your
using a database like SQL Server to store your data) Since you are
running in batch you have no performance issues.

As I indicated, there are some tricks with RTVJRNE. I have some sample
code that handles the tricks.

On Tue, Jun 12, 2012 at 2:09 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

OK thanks for all the feedback.

For this ETL project we have decided to try journals, for all the reasons everyone here explained.

Mostly due to requirements of file lock to modify trigger pgm, and instant updates to remote system is not required.

Plan is to RTVJRNE records for specific files/dates/times and save off record keys.

Each night, sort down keys and send CURRENT data record of that key which had changed data (don't send journal data).

Any suggestions regarding how to use journal files to accomplish this?  Or pitfalls to avoid?

Thanks



______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


________________________________________________________________________
This inbound email has been scanned for all viruses by the MessageLabs SkyScan
service.
________________________________________________________________________

______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.