Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: How to design tables to hold cube data?
In article <950tc1$g2d$1_at_nnrp1.deja.com>,
lawr99_at_hotmail.com wrote:
> Here is the problem, you have clients who will need to input revenue
> information into the database. Some might just want to break this up
> into years, but others may want to break revenues further into
> regions. Some might even want to break it down into seasons. There
is
> no telling up front how many different ways this data will be looked
> at. The cube has to be able to go to the nth level.
>
> How can you design a table structure to handle this?
>
> Sent via Deja.com
> http://www.deja.com/
>
-- I would suggest adding OMNIDEX indexing to the database to get good performance no matter how many different ways the data will be looked at. For more information, see http://www.disc.com/home or contact me. Cheryl Grandy cgrandy_at_disc.com 303 444-4000 Get OMNIDEX for the fastest applications ever Sent via Deja.com http://www.deja.com/Received on Mon Feb 05 2001 - 17:45:39 CST