Oracle Star Database

Previous TopicNext TopicContents

The Oracle Star Database contains a dimensional data model along with several fact tables (including UDF fact tables and history fact tables (if configured)) and the supporting dimensions. Excluding the configurable history data tables, the Star Database will contain fewer rows because baseline projects are not directly accessible.The Oracle Star database is still much smaller than Oracle ODS Database.

The fact data represents the largest portion of data in the Oracle Star Database. As with any Star schema, this data is the most granular data built to support roll-up queries.

Depending on the History Interval and History Level settings, the Activity, WBS history tables and Slowly Changing Dimension (_HD) tables are likely to be the largest.

The primary two fact tables contain activity and resource assignment spread data respectively. The size of these tables will be the same as the corresponding Oracle ODS Database tables (ActivitySpread and ResourceAssignmentSpread).

The next largest fact table contains resource utilization data (W_RESOURCE_LIMIT_F). This differs from other fact tables in that the data size is not a function of the number or size of projects. Instead, it is a function of the number of resources in the database, and the size of the data warehouse reporting window. There is a daily value for everyday of the reporting period, and for each resource. For example, if the reporting window spans five years (1,825 days), and there are 1,000 resources in the database, the total recorded in the fact table will be 1,825,000.

The Project History fact table is the smallest and it has only project-level data. The difference is that this table is a trending table with snapshots of the data over time. The number of snapshots depends on the interval chosen during installation (weekly, monthly, financial period). The granularity of this fact table goes to only the project-level; it contains no spread information. Calculate the number of rows using the total non-baseline projects times the number of snapshots. This will grow over time, so the yearly total for a 10,000 project database with weekly snapshots will be 520,000 rows.



Legal Notices
Copyright © 1999, 2014, Oracle and/or its affiliates. All rights reserved.

Last Published Friday, January 31, 2014