Re: Reports in OLTP system

From: DA Morgan <damorgan_at_psoug.org>
Date: Tue, 31 Jul 2007 15:52:25 -0700
Message-ID: <1185922343.311586@bubbleator.drizzle.com>

Wiktor Moskwa wrote:
> On 29.07.2007, DA Morgan <damorgan_at_psoug.org> wrote:

>> Wiktor Moskwa wrote:
>>> Well, I want to learn how such things are done.
>>> Are materialized views or advanced queuing right tools
>>> here or not.
>> To determine that would be a full scale research project. They might
>> be and then again they might not be. I know organizations doing it
>> with Data Guard replication to a logical standby so it very much
>> depends.

>
> Thanks for a reply. Let me change my question a little.
> I wonder what is a usual practice of serving aggregate data in
> a standard database (not a warehouse, used to store current data).
> By aggregate data I mean for example monthly sales summary.
>
> The example environment is a web application with 2000 users
> (each is a different <very> small business, not related to others,
> with distinct subset of data). How to provide them with effective
> up-to-date summaries? (triggers? MVs? queuing? calculation on
> request and storing for later use?)
>
> And a sub-question: with two tables INVOICE (parent) and
> INVOICE_ITEM (child) - do you usually keep sum of values
> from child rows in parent row or calculate in application
> every time?
>
> Thanks in advance.

Depends on the SLA. What is your obligations with respect to security, auditing, backup and recovery, etc.

My preference would be replication to a logical standby but finances are always a factor.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Tue Jul 31 2007 - 17:52:25 CDT