|
We are journaling. I assume you've got to be really careful with using
that if you value the data integrity. I mean, you've got to track where
the journal was last read, be aware of all the possible journal entry types
you might encounter, and then watch out for someone refreshing the
warehouse files, which would require setting a new point in the journal
reading jobs. I was hoping to avoid a lot of that.
After I sent my initial request, I found something about MQT tables being
updated incrementally with something called a staging table. I find very
little documentation when I google for anything about staging tables, so,
I'm wondering if that's an option that someone has had success with.
From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/12/2015 04:00 PM
Subject: Re: Incremental update for files
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Are you journaling your production files? If so, you could use your
journals to add or update your data warehouse files.
Regards,
Luis
Sent from my Moto G phone. Please excuse my brevity.
On Jun 12, 2015 3:04 PM, <darren@xxxxxxxxx> wrote:
So,
We're planning to do a daily snapshot of a bunch of production data
(millions of records) for a data warehouse/reporting tool called Cognos.
The refresh takes quite a bit of time, and a lot of it is historical.
are there any options for net changing or incremental refreshing theselist
files? We're avoiding using production files directly for a number of
reasons. One of them is that we're also building quite a few summary
tables, and the detail needs to match up with the summary data, which it
would not, if transactions are happening during the day.
___________________________________
Darren Strong
Programmer/Analyst
Group Dekko, Inc.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.