Start of Content Area

Function documentation Maintenance of Statistics Properties  Locate the document in its SAP Library structure

Use

Within the scope of BI query runtime statistics, the system can collect data for the following types of BI objects:

      BEx query

      BEx Web template

      BEx workbook

      InfoProvider (with restrictions)

On the Maintenance of Statistics Properties screen (transaction RSDDSTAT), you can edit the statistics properties for individual objects as well as the default settings for the object types listed above.

Note

Maintaining the statistics properties of a BEx Web template or a BEx workbook only has an effect on the creation of the respective front end runtimes. However, maintaining the statistics properties for queries (or InfoProviders) only affects runtimes in the analytic engine and in the data manager. A complete recording of the runtime (data manager – analytic engine – front end) is, therefore, only guaranteed if the statistics properties are maintained for the relevant query and front end objects.

Note that the system records a large amount of detailed runtime data as part of the BI query runtime statistics. Recording the runtime of a navigation step for a query can generate on average 20-40 records, depending on the level of detail of the statistics. Deactivate the detailed runtime recording for all objects for which you do not require performance analyses.

Integration

From the Data Warehousing Workbench screen, you can navigate to the maintenance for the statistics properties by choosing Tools Settings for BI Statistics.

Features

Changing Statistics Properties

The various objects are located on the corresponding tab pages. You can use the sorting and filter functions for the table to preselect the objects to be changed.

...

       1.      Select the objects you want to change.

       2.      Select the required settings using the Settings selection list for the object. You can choose whether the statistics are to be switched on or off, or you can choose the default setting (D) for the object type. For queries, you can also specify the detail level for the statistics.

       3.      To apply the settings to the list, choose This graphic is explained in the accompanying text Replace Values. The system sets the relevant indicator in the Last Changed column.

       4.      Choose This graphic is explained in the accompanying text.

Default Setting for Object Types

Every new object initially has the default setting for its object type as the statistics property.

To change this setting, choose Extras  Change Default. The dialog box with the current default settings for the object type appears; you can change the default values here. All objects of this type with "D" in the Statistics On/Off column are then treated according to the new default setting when statistics are recorded.

An exception to this rule is the Query object type: if no specific statistics property is set for a query, that is, the default value "D" is set, the system first determines the statistics property for the InfoProvider of the query. If the InfoProvider has the value "D" as the statistics property, the system reverts to the default setting for the query; otherwise, it uses the InfoProvider setting (with the OLAP detail level from the InfoProvider setting).

Example

A new query is created. It has the statistics setting "D". The default setting for the query is Statistics Off. The InfoProvider for the query, however, explicitly has the setting Statistics On (not as default setting). In this particular case, the system records statistics data for the query.

Note

This derivation relates only to the InfoProvider on which the query is directly based. If this involves a MultiProvider, no additional derivation is made of the possible settings from the InfoProviders contained the MultiProvider.

Statistics Detail Level for the Query Object Type

For queries, you also have the option of selecting a detail level for the statistics data. You can choose from the following:

      0 – Aggregated Data: The system writes only one OLAP event (event 99999) for the query. This contains the cumulative times within the OLAP processing of the query. The system does not record data from the aggregation layer of the analytic engine or aggregation information.

      1 – Only Front End/Calculation Layer Data: The system records all OLAP events, but not separate data from the aggregation layer of the analytic engine.  The system writes only the general data manager event 9000 in the OLAP context as well as the aggregation information.

      2 – All: The system records all data from the area for the front end and calculation layer as well as data from the area for the aggregation layer and aggregation information.

      9 – No Data: The system does not record any data from the front end and calculation layer or from the aggregated event 99999. However, it does record data for the BEx Web templates and workbooks, depending on the setting.

Caution

When you select the detail level, keep in mind that a very large amount of data is recorded when the system records data manager times.

Example

A Web template with four queries is executed. Each query is based on a MultiProvider that contains ten InfoProviders; each of these InfoProviders has data in the E table and F table. Due to specific query properties, the query is split into two parts. Each part is based on a different aggregate.

This results in: 4 queries * 10 InfoProviders * 2 parts * 2 table types = 160 records in the RSDDSTAT_DM table view (plus the records from the area for the front end and calculation layer of the analytic engine in the RSDDSTAT_OLAP table view).

InfoProvider Tab Page

In addition to the default setting described for queries of an InfoProvider, you can also change the following statistics properties for an InfoProvider:

      Statistics data for aggregate processes (fill, roll up, change run, condense): You can switch the recording on or off.

The recorded data is stored in the RSDDSTATAGGR table.

      Data from the aggregation layer for the external BI read interface (RSDRI): You can switch the recording on or off.

Since queries through the external read interface do not run through the OLAP processor, for this type of request, the system records only the event 9001 (External Read Interface) with the handle type EXTN in the area for front end and calculation layer. Processing in the area for the aggregation layer does not differ from a "normal" BEx query; the relevant statistics can therefore be recorded for this.

Note

For InfoProviders, the statistics detail level relates to the default setting for the queries of the InfoProvider only, and not to the processes listed above.

Deleting Statistics Data

Data for BI query runtime statistics is to be deleted when the data is loaded into the InfoCubes of the technical content. The DataSources 0TCT_DS01, 0TCT_DS02 and 0TCT_DS03 automatically delete all data from the underlying statistics tables that are older than 14 days as part of a delta upload. If necessary, this interval can be defined on a customer-specific basis in the table RSADMIN using the parameter TCT_KEEP_OLAP_DM_DATA_N_DAYS.

Note

Refer to the SAP Note 891740.

When you choose This graphic is explained in the accompanying text Delete Statistical Data, the dialog box for restricting the areas in which the statistics data is to be deleted appears. You can select multiple areas.

      Query Statistics Tables: The system deletes the data for BI query runtime statistics.

      Aggregates/BIA Index Processes: See Statistics for Maintenance Processes of SAP NetWeaver BI Accelerator Indexes.

      InfoCube Statistics (Delete, Compress): The system deletes the data of the InfoCube statistics that results when data is deleted from an InfoCube or when data requests of an InfoCube are compressed.

Using the Up to Day (Incl.) field, you can enter a date up until which the system is to delete the statistics data. If you do not enter a date, all data is deleted. Since this can be executed with a command (TRUNCATE TABLE), (and not using selective deletion in the database), this version is considerably faster.

By restricting to one day, packages of 1000 records only are always deleted from the tables; this is followed by a database Commit. This makes it possible to restart after a termination (resulting from a TIMEOUT, for example), without a need to redo previous work.

Note

You can also use the RSDDSTAT_DATA_DELETE program to delete data from the statistics tables. The dialog box mentioned above for restricting the areas from which the data is to be deleted is also displayed when you use this program.

 

 

End of Content Area