Re: Client/Server query strategy

chuckh_at_ix.netcom.com (Chuck Hamilton) wrote:
>Just out of curiousity, even in a heavy OLTP database, couldn't you
>insure that the detail and aggregate tables are always in sync via
>triggers or stored procedures? (If this is a dumb question, remember I'm
>an Oracle novice.)
>
> ><> Chuck Hamilton <><

In principle, sure. HOWEVER, how long does it take to create the aggregate? Does doing the aggregate consume significant CPU resources? If the OLTP trasnaction rate is such that the (average) time between transactions is less than the time it takes to do the aggregation, you face the possibility of having the whole system brought to its knees by the constant triggering of the aggregation. Even if the transaction rate is fairly "slow" (whatever represents, "slow" in a given situation) you still could be out of sync for the time it takes to do the aggregation.

In short, there are no panaceas. You have to _thoroughly_ understand the system, the application and the customer's requirements and then do the "right thing" based on that thorough understanding.

--
Bill Meahan,  Senior Developer  |        wmeahan_at_ef0424.efhd.ford.com
Electrical & Fuel Handling Division, Ford Motor Company
Opions expressed herein are those of the author and in no way represent
any official statement or opinion of Ford Motor Company