How to design tables to hold cube data?

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/ Received on Sun Jan 28 2001 - 04:47:30 CST