A key benefit of using the Schema Generator is that the database
administrator (DBA) does not have to manually create the Cube Views™ schema
using the online analytical processing (OLAP) center. It automatically generates
a Cube
Views XML file, which contains cube models and cubes to support the business measures model.
The Schema Generator uses the business measures model to
produce a DB2® Cube
Views XML file. This XML file contains information that describes the
star schema associated with this business measures model.
After the generation of the schema, the DBA must deploy the generated DDL
scripts, which create additional database tables in the Historical database.
Next, the DBA uses the OLAP center to manually import the Cube Views schema.
Important: - All databases and related static tables are created before the Cube Views schema
is deployed.
- The DDL that is generated to represent the running database tables must
be executed before the Cube Views metadata is executed.
The Schema Generator maps the
business measures model to
a simple star schema representation, which will be deployed in the OLAP center.
Some key points to note about how the Cube Views schema is generated are:
- A cube model is created for each business measures group. The name of
the cube model is derived from the business measures model.
- A fact table exists for each business measures group. The fact table name
is defined in the business measures model.
- For each metric, there may be one or more aggregation types (such as SUM,
AVG, COUNT, MAX, or MIN) and a corresponding measure name.
- The schema name is specified at the time the product is installed. The
Launchpad collects the schema name during the installation process.
- The cube model and cubes are based on the most current business measures model.
Any change in the business measures model requires
regenerating and redeploying the Cube Views metadata.