Collection and reorganization schemata of the Central Performance History (CPH) specify how long data assigned to this schema are to be stored in the CPH with which granularity. You can create your own schemata and use the schemata delivered by SAP.
If you want to use a standard schema of this type, you should first answer the following questions:
· With what granularity should the measured values first be collected in the CPH?
· With what granularity should the measured values be stored long-term in the CPH?
Depending on how you answer these questions, we recommend one or more of the following schemata:
|Granularity of Measured Values||Granularity of the Long-Term Storage|
The granularity of the measured values and the aggregates to be stored long-term can be determined from the names of the standard schemata. The naming convention is as follows:
SAP_<Granularity of the measured values>__NO_AGGREGATION orSAP_<Granularity of the measured values>_WITH_AGGR_TO_<Granularity of the aggregates>
Use the standard schemata if these are suitable for your requirements for collecting and reorganizing performance values. You can also use these schemata as templates for your own collection and reorganization schemata. This is useful, if their structure (which values are collected) suits your needs, but you want to change the storage period for individual aggregates (see Maintaining a Collection and Reorganization Schema (Default Setting)).
SAP delivers the following standard schemata:
This schema exists primarily to ensure that the CPH remains compatible with previous versions, with which this schema was always delivered. This is less suitable as a schema for productive use of the CPH due to the short storage period.
This schema stores hourly values for 36 days. This number was chosen to ensure that, even when public holidays fall on awkward days (such as after Easter), the data is still available for all days of the previous month on the first workday of a month.
Use this schema if you require hourly values, but long-term storage of the measured values or their aggregation is not necessary, such as when the long-term archiving should be performed exclusively through reporting.
This schema stores hourly values for 36 days and aggregates the values to monthly and yearly aggregates with an hourly granularity. If you do not require minute or quarter-hourly values, we recommend this schema.
This schema stores hourly values for 36 days and aggregates the values to monthly and yearly aggregates with a daily granularity. Use this schema if you require hourly values and long-term storage in this granularity is not necessary, but you require at least daily values to identify long-term trends.
This schema corresponds in large part to SAP_HOUR_COLLECTION_WITH_AGGR_TO_DAY, however quarter-hourly values are also collected and stored for 15 days. Use this schema if you require quarter-hourly values.
This schema corresponds in large part to SAP_HOUR_COLLECTION_WITH_AGGR_TO_DAY, however minute values are also collected and stored for 15 days; these minute values are then aggregated to quarter-hourly values and stored for 36 days.
Note that the collection of minute values produces a significantly higher workload; first, the collection job responsible runs significantly more often, and second, a significantly higher network load is produced by the higher quantities of data transferred.
This schema corresponds in large part to SAP_HOUR_COLLECTION_WITH_AGGR_TO_HOUR, however minute values are also collected and stored for 15 days; these minute values are then aggregated to quarter-hourly values and stored for 36 days. If you require minute values, we recommend this schema.
This schema stores minute values for eight days, no aggregation is performed. Use this schema if your require minute values, but do not require long-term storage of the values, or realize this by, for example, reports that run daily.