Oracle Database Enterprise Edition with Partitioning is the solution for growth over time within the history tables. While Oracle recommends that you use a partitioned environment, Primavera Data Warehouse also supports non-partitioned environments.
Note: If you are connecting multiple P6 EPPM or Primavera Unifier data sources to Primavera Data Warehouse, you must enable partitioning.
If you do not use a partitioned environment, Oracle recommends that the P6 EPPM database and/or Primavera Unifier database be a "small-sized database" as defined in Planning for the Impact of P6 EPPM on Primavera Data Warehouse. Partitioning helps keep performance consistent over time for each STARETL process run. This is particularly important when enabling activity or WBS-level history. Without partitioning, you should not use activity and WBS-level history gathering.
Without partitioning, the amount of time required to run the STARETL process increases over time. As the size and row count of specific Primavera Data Warehouse tables increases (w_project_history_f, w_wbs_history_f, w_activity_history_f, as well as tables ending in _HF and _HD) the need for partitioning also increases. You can monitor the run times for each STARETL process with the logs and reports located in <PDW Install Folder>\star\etl_homes\staretl<id>\log. See the Primavera Data Warehouse Installation and Configuration Guide for details on log files.
If you deploy without partitioning, the following features are not supported:
- WBS-level or activity-level history transfer to Primavera Data Warehouse
- WBS-level or assignment-level history transfer to Primavera Data Warehouse
- Multiple data sources
- Burn Down functionality
- Work Planning functionality
- Capturing dimensional history
Note: If you implement partitioning, you must license the Oracle Database partitioning option.