eG Help

BEx queries filter the data to create reporting objects or views called InfoProviders. Some InfoProviders contain actual data. Others provide views of data stored in elsewhere. Using queries, the data can be quickly targeted and evaluated. The more precisely the query is defined, the query can be navigated and refreshed at a faster pace.

Query runtime statistics are used to analyse the average query execution time in different layers such as front end, OLAP or data manager. This can also be used to determine the execution time of certain user actions in the front end and in the analytic engine. The system records all these processing steps in the statistical tables, which are known as statistics events. It calculates the net time taken for processing of a query by calculating the runtime of an event using the difference between the start and end time. If the queries do not execute faster or if the queries fail to execute, then the data could not be retrieved and generated for the target SAP Business Warehouse instance. To proactively figure out the queries that are taking too long to execute and to figure out where exactly the queries spend most of the time upon execution, administrators can use the BWQueryStatTest.

This test auto-discovers the queriess created on the target SAP Business Warehouse instance and for each query, this test reports the number of sessions that initiated the query. In addition, this test reports the number of times each query was executed and the time taken by each query for execution. Using this test, administrators can figure out the query that is the slowest to execute. Also, this test throws light on where exactly the query took too long to execute - is it in the front end? or OLAP? or data manager package?

Outputs of the test : One set of results for each workbook created on the target SAP Business Warehouse Instance being monitored.

Measurement	Description	Measurement Unit	Interpretation
Sessions	Indicates the number of sessions in which this query was initiated during the last measurement period.	Number	A high value for this measure is a indication that the query is called for frequent execution. This may sometimes lead to slowness in query execution.
Steps	Indicates the number of steps that were executed for this query during the last measurement period.	Number	A high value for this is an indication that the query is slow to execute.
Executions	Indicates the number of times this query was executed during the last measurement period.	Number	This measure is a good indicator of load on the SAP Business Warehouse Instance. Compare the value of this measure across workbooks to figure out the workbook that is executed more frequently.
Execution_rate	Indicates rate at which this query was executed during the last measurement period.	Execution/min
Selected_records	Indicates the number of records that were selected from the database by this query upon an execution.	Records/execution
Transported_records	Indicates the number of records that were transported from the database by this query upon an execution.	Records/execution
Response_time	Indicates time taken by this query to complete an execution.	Seconds/execution	Compare the value of this measure across workbooks to figure out the workbook that is the slowest in terms of execution. Use the detailed diagnosis of this measure to figure out the executions that were the slowest for each workbook. The detailed diagnosis of this measure lists the name of the user, Start time, Info provider, Selected records, Transported records, Response time, OLAP time, OLAP cache time, Data manager time, OLAP authorization time, OLAP input help time, OLAP services time, Query Generation time, Data read time, Data selection time, Front end data transfer time, Read texts time, Badi compute time, Other events time, Properties, Session ID, Step ID and HandleID.
OLAP_time	Indicates the Online Analytical processing time taken per execution by this query.	Seconds/execution
OLAP_cache_time	Indicates the average OLAP time taken by this query for cache operations upon an execution.		Cache operations comprises of generation of cache entry, read from cache, write to cache, and deletion of cache entries.
Data_manager_time	Indicates the time taken by this query to collect data from the data manager package upon execution.	Seconds/execution
Olap_authorization_time	Indicates the OLAP time taken by this query for all authorization upon an execution.	Seconds/execution	The value of this measure is a sum of time taken to determine the authorized individuals and intervals, time taken to determine authorized hierarchy nodes, check the authorizations and buffer authorizations.
Olap_input_help_time	Indicates the OLAP time taken by this query to generate input help upon an execution.	Seconds/execution	This measure is the sum of the time taken for value help, value help DB and value help for hierarchy nodes.
Olap_service_time	Indicates the OLAP time taken by this query to complete processing the data upon an execution.	Seconds/execution
Query_generation_time	Indicates the average time taken by this query to check the query definition and generate the output upon an execution.	Seconds/execution
Data_read_time	Indicates the time taken by this query to collect the requested data from the data manager package or from the OLAP cache upon an execution.	Seconds/execution
Data_selection_time	Indicates the time taken by this query to query the data manager package in order to sort the read data according to structure element selection or a restricted key figure upon an execution.	Seconds/execution
Front_end_data_transfer	Indicates the time taken by this query to transfer data to the front end upon execution.	Seconds/execution
Read_texts_time	Indicates the time taken by this query to read the text from the data upon an execution.	Seconds/execution
Badi_compute_time	Indicates the time taken by this query to execute business add in or user exit.	Seconds/execution
OLAP_other_time	Indicates the time taken by this query to perform other events/activities upon an execution.	Seconds/execution