Vous êtes sur la page 1sur 7

Maintenance of Statistics Properties

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. 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 Replace Values. The system sets the relevant indicator in the Last Changed column. 4. Choose . 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). 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. 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. 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. 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. 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. Refer to the SAP Note 891740. When you choose 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. 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.

BI Statistics
Architecture
BI statistics allow you to record runtime data for BI processes and events in the BI suite, Analytic Engine and in the Data Warehouse. The system records the performance-critical parts of the processing (statistics events). It calculates the net times by calculating the runtime of an event

using the difference between the start and end times (minus the times for other events called from within the event). You can also use the statistics to record the monitoring status of BI objects from the Data Warehouse. Technical BI Content provides you with predefined BI objects for analyzing statistics data. BI Administration Cockpit provides a central point of entry to the web templates in Technical BI Content. The BI Administration Cockpit enables integration with other portal entities, such as the universal worklist. The graphic below illustrates the architecture of BI Administration Cockpit. The interaction between BI statistics, technical BI Content and BI Administration Cockpit is based on this architecture:

Recording BI Statistics
BI statistics are recorded for the following areas: BI query runtimes (actions on the front end and in the Analytic Engine, including BI Integrated Planning) In Data Warehousing Workbench, you can set which objects the system will record statistics for by choosing Tools BI Statistics Settings. Runtimes of subprocesses in SAP NetWeaver BIA index maintenance In Data Warehousing Workbench, you can set which objects the system will record statistics for by choosing Tools BI Statistics Settings.

Runtimes and status of data transfer and data processing in the Data Warehouse The system always records statistics on the runtimes and status of data transfer and data processing in the Data Warehouse. This is not the case for statistics for the data transfer process. These are deactivated in the default setting and can be activated in table RSDDSTATOBJLEVEL. More information: SAP Note 966964. Runtimes for performing planning functions Depending on the area, the system writes the statistics recordings to tables RSDDSTAT* or UPC_STATISTIC*. For statistical analyses in Data Warehouse processes, tables

RSMDATASTATE, RSMDATASTATE_EXT, RSDDSTATDTP, RSBKREQUEST, RSBSOURCEPROP, RSPCLOGCHAIN, RSPCPROCESSLOG are used too.

Analyzing BI Statistics
You have a number of options for analyzing statistics data. These options are illustrated in the following graphic and described below:

Analysis Using the Tables or Views You can analyze the tables and views directly in the data browser (transaction SE16). Analysis of query runtime statistics is simplified using views RSDDSTAT_OLAP and RSSDDSTAT_DM. When analyzing the runtimes and status for the load and maintenance processes in Data Warehouse, tables RSDDSTATWHM and RSDDSTATDTP are particularly relevant. Runtimes of subprocesses in SAP NetWeaver BIA index maintenance are analyzed in table RSDDSTATTREX. Runtimes of planning functions are analyzed in table UPC_STATISTIC*. Analysis Using Technical BI Content for BI Statistics Technical BI Content provides predefined BI objects for analyzing most statistics data. The data is stored in the relevant InfoProviders. Queries and Web templates enable flexible analysis and differentiated display of information, for example using charts, table or graphics. While analyzing the statistics data using the technical BI Content provided is mandatory, you can define your own queries and Web templates to run analyses with. You can therefore take content from standard Web templates and combine it to make your own Web template. In the BI system, you can run technical content queries using Query Monitor (transaction RSRT). Prerequisite: You have activated technical BI Content. For more information, call Customizing and choose SAP NetWeaver Business Intelligence Settings for BI Content Business Intelligence BI Administration Cockpit Activate Technical Content in SAP NetWeaver BI.

We recommend using technical BI Content from SAP NetWeaver 7.0 BI Content Add-On 3 or higher. Analysis (Technical Content) Using the Workload Monitor (ST03) The workload monitor contains the function BI System Load, which you can use to analyze statistics data. The analysis is based on the technical content. Analysis (Technical Content) Using BI Administration Cockpit BI Administration Cockpit offers you a central point of entry to the web templates in the technical content. It provides you with an overview of critical situations in query runtime and the runtime and status of load and processing processes in the Data Warehouse. You can navigate to detailed information and to troubleshooting and optimization applications. See SAP Note 934848 (collective Note; (FAQ) BI Administration Cockpit) Requirements: You have activated the technical content. You have installed Business Package BI Administration 1.0. You have made the other settings required. For more information, call Customizing and choose SAP NetWeaver Business Intelligence Settings for BI Content Business Intelligence BI Administration Cockpit. If you want to call BI Administration Cockpit from the BIS system, make the Customizing settings SAP NetWeaver Business Intelligence General BI Settings Settings for the Administration Cockpit. As explained under Analysis Using Technical BI Content for BI Statistics, you can also use the InfoProviders, queries and Web templates used in BI Administration Cockpit without the portal, thus combining the standard Web templates into a Web template of your own. Ad Hoc Analysis of Query Runtime Statistics You can run an ad hoc analysis of the query runtime in Query Monitor. You can display runtime statistics for Web applications by using URL parameter &PROFILING=X in the start URL of a Web application. More information: Displaying BI Query Runtime Statistics on the Web Direct Access to Statistics Tables Using Technical Content As well as analysis scenarios based on persistently stored data, you can also access statistics data directly. With persistent data storage, the statistics data is extracted from the tables in scheduled processes and stored in the relevant InfoProviders. If you want to analyze the data in real time, you can use the VirtualProvider tool in the technical BI content to read the data in the tables directly from the query or Web application. Taking query runtime statistics as an example, the graphic below illustrates how you can use a MultiProvider to read periodically loaded delta data (recommendation: daily) from the InfoCube and to read delta data that has not been loaded yet directly from the statistics tables using a VirtualProvider.

Deleting Statistics Recordings


Query runtime statistics in particular generate a large amount of statistics data in the BI statistics tables Depending on the (user-defined) delta statistics level, between 20 and 80 data records are written to the BI statistics tables for each single navigation step. We therefore recommend loading the statistics data into the technical content and deleting the original data from BI statistics tables RSSDDSTAT* and UPC_STATISTIC* on a regular basis. When using technical content, deletion of statistics recording for query runtime statistics is automated. For more information about this and about manually deleting data from RSDDSTAT tables, see Maintenance of Statistics Properties. In transaction BPS_STAT0, you can delete statistics data from the UPC_STATISTIC* tables. You can enter a date for deletion of table entries. The system then deletes all entries whose recording date is earlier than the date you entered.

More Information
BI Statistics Recordings BI Query Runtime Statistics Overview of Statistics Events (Table RSDDSTATEVENTS) Statistics for Maintenance Processes in a SAP NetWeaver BI Accelerator Index Analysis of BI Statistics Recordings Technical Content in BI Administration Cockpit BI Administration Cockpit

http://help.sap.com/saphelp_nw70/helpdata/en/44/08a75d19e32d2fe1000000 0a11466f/frameset.htm