Databases Reference
In-Depth Information
Study carefully how the
MYR 2009
number can be easily added to the
MYR 2010
number to give us the
Total Model Year
number.
This is a highly simplified example of an Essbase database outline, its structure, and
relationships. In the next chapter, we will go over the Essbase database outline much
more thoroughly.
In the next section, we shall use what we have learned here to make decisions on
the best methods to store data in our Essbase database.
Determine data storage options
Get ready to toss out everything you've ever learned about storing data in a typical
relational database with tables, rows, and columns. Keeping the above example of
the Essbase outline in mind, we will now begin covering how the data is stored in
Essbase and the various options available to you (the Essbase programmer).
An Essbase cube usually stores less physical data than a typical relational
database must store to deliver the same results to the user. Usually,
the greatest saving is in the expense of data retrieval times. The results
returned from a typical Essbase database require less processing overhead
than the similar results being delivered as the result of queries performed
against relational database tables.
Essbase stores data in what is commonly referred to as a multidimensional array.
