SAP BW Performance Monitoring with BW Statistics

Know How Network: SAP BW Performance Monitoring with BW Statistics

Ron Silberstein Platinum Consultant Netweaver RIG US SAP Labs, LLC

- Business Intelligence

2003 SAP Labs, LLC, SAP Professional Journal Conference, Ron Silberstein 2

Agenda

Monitoring with BW Statistics Reports

Performance Monitoring Tools

BW Statistics Overview

Detecting Optimization Potential

Setting Up BW Statistics

2


Agenda

BW Statistics Overview

3


BW Statistics: Facts

SAP-delivered tools for analyzing and tuning system performance

Delivered SAP Business Content

Usage of tools requires Business Content installation

Content Delivery Consists of: MultiCube InfoCubes Queries Workbook (New one as of BW 2.0B) InfoSources Transfer Structures, Transfer Rules, Update Rules InfoPackages, InfoPackage Groups Role

4


BW Statistics: Facts (continued)

Maintenance requires scheduling data loads and monitoring Delta load functionality delivered Transaction Data Master Data

One of several sources of performance monitoring information. Others include:

ST03 > Expert Mode > BW system load Table RSDDSTAT Function Module RSDDCVER_RFC_BW_STATISTICS

Can be utilized when building aggregates System can “propose” aggregates from BW stats data

Object metadata of BW Statistics is transportable

5


BW StatisticsMultiProvider

QueriesQueries

aggregatesaggregates

warehousemanagementwarehouse

management

Table RSDDSTAT

Analysis by queries

(in workbooks)

Table RSDDSTATAGGR

Table RSDDSTATWHM

Info-SourceInfo-

Source

Turn on/off logging for each InfoCube!

Updaterules

Updaterules

BW Statistics: Data Flow Architecture

Info-SourceInfo-

Source

Info-SourceInfo-

SourceUpdaterules

Updaterules

Updaterules

Updaterules

6


Enable Capture of Statistical Performance Data

Choose Tools > BW Statistics for InfoProviders

Can be turned on/off for OLAP/WHM

You can delete old data from database tables

You can store new settings permanently

7


Consequences

If the BW statistics are turned on, the systems collects data. These data is inserted in different tables:

Tables, which are filled by ‚OLAP‘:

RSDDSTAT

RSDDSTATAGGR

RSDDSTATAGGRDEF

Tables, which are filled by ‚WHM‘:

RSDDSTATWHM

RSDDSTATCOND

RSDDSTATDELE, ...

8


Agenda

Monitoring with BW Statistics Reports

9


Key Delivered Queries (BW Statistics Workbook)

Use of OLAP for Each InfoCube (Time) Components of runtime per query

Use of OLAP for Each InfoCube (Records) Records selected / transferred

Query Runtime User, query, # of navigations, components of runtime

Use of OLAP by Date

Use of OLAP according to time of day

Mean Time Per Query Mean time per navigation

Data Load: Utilizing WHM per InfoSource

10


Example: SAP Delivered Graph (Workbook)

Total runtime (blue) by hour andTotal number of records (red) by hour

11


# of Navigations

Customer Report Example: Usage by Month (Cube)12


Enterprise view# of navigations

by user

Customer Report Example: Usage by Month (User)13


InfoCube view# of navigations

by user

Example: Usage by Month (User) for a Cube14


Customer Example: Aggregate Use Per Cube15


Customer Example: Aggregate Use Per Cube16


Agenda

Performance Monitoring Tools

17


Overview: Reporting Performance Analysis Tools

Table RSDDSTAT

Function module RSDDCVER_RFC_BW_STATISTICS

BW Statistics

Collecting information from table RSDDSTAT

BW Workload Analysis – ST03N

18


Expert mode

Expert mode

Administrator

SService engineer

ST03 – Workload Analysis – BW Specific

1

2BW System Load

19


ST03 - WorkLoad By InfoCube

Highest contributor in Total Run Time per

InfoCube

High % DB Time

High ratio:

Selected / transferred

records

Expert Mode!

20


In transaction SE16, display table RSDDSTAT

Using Table RSDDSTAT

INFOCUBE

QUERYID

QRUNTIMECATEGORY

QNAVSTEP

QDBSEL

QDBTRANS

QTIMEDB

STARTTIME

Width of output list

Maximum no. of hits

Number of entries

to

to

to

to

to

to

to

to

YYYYMMDDHHmmss

21


Choose Settings User parameters (F6)

Settings of Table RSDDSTAT

INFOCUBEQUERYIDQRUNTIMECATEGORYQNAVSTEPQDBSELQDBTRANSQTIMEDBSTARTTIME

Width of output listMaximum no. of hits

Repository Infosystem Data Browser ITS Chan...

User-Specific Settings

Output listWidth of output listMaximum no. of hits

Display max.n.of hits possibleALV-GridALV-ListSE16 standard list

KeywordField nameField text

Check conversion exits

Set flag to display query names

22


Important Fields in Table RSDDSTAT (1)

Query name Runtime Category Database time Records selected on the database

Records transferred

from the database to the OLAP

23


Agenda

Detecting Optimization Potential

24


Analyzing Reporting Performance Issues

Building Aggregates:

Primary technique for tuning reporting performance Analyze to determine if building aggregates will help

Different Starting Points:

Analyze specific InfoProviders

OR

Find problem queries, then analyze them

25



Approach: Find InfoCubes of concern & consider aggregates

26


BW Statistics or ST03N: Find InfoCubes for Analysis

Sort by mean overall time to find InfoCubes with queries having the highest runtimes

27


Front-end

Database Server

Stastistics for Queries

Application Server

InfoCubeData

Queryexecution

BExAnalyzer

WebBrowser

OLAPprocessor

Front-end time?

OLAP time?

Database time?Number of rows

selected on the database?

Number of rows transferred to the

application server?

Amount of data

transferred to the front-end?

1

2

3

Aggregates

28


Indicators That Aggregates Will Help

Infocube Number of records read on the database (QDBSEL)

Records transferred after being summarized on the database (QDBTRANS)

Start 2s 4s 6s 8s 10s 12s 14s 16s 18s 20s

Total query runtime (QRUNTIMECATEGORY)

End

Database time (QDBTIME)

Other Key Indicator:

database time for queries > 30% of total query runtime

One Key Indicator:

Ratio records selected / records transferred > 10

Look for many more records selected than necessary!

29

AND


Analysis of BW Statistics at InfoCube Level (1)

Database time ~40% of total runtime (6771 of 17 025 seconds)

Ratio records selected / records transferred: 24

Aggregates will probably

improve query performance

30


Database time ~3,5% of total runtime (1011 of 28 540 seconds)


Aggregates will not improve

query performance

Analysis of BW Statistics at InfoCube Level (2)31


Database time ~90% of total runtime (1420 of 1572 seconds)


query performance

Ratio records selected / records transferred: 1.1

Analysis of BW Statistics at InfoCube Level (3)32



Approach: Find queries of concern, then analyze them

33


Indicators That Aggregates Will Help

Infocube Number of records read on the database (QDBSEL)

Records transferred after being summarized on the database (QDBTRANS)

Start 2s 4s 6s 8s 10s 12s 14s 16s 18s 20s

Total query runtime (QRUNTIMECATEGORY)

End

Database time (QDBTIME)

Other Key Indicator:

database time for queries > 30% of total query runtime

One Key Indicator:

Ratio records selected / records transferred > 10

Look for many more records selected than necessary!

29

AND


Utilizing OLAP per QuerySort by overall time to find queries that have the highest total runtime

Using BW Statistics: Find Queries for Analysis35


Utilizing OLAP per QueryDatabase time ~60% of total runtime (2.798 of 4.685 seconds)


Aggregates will improve

query performance

Analysis Techniques: Key Components of Runtime 136


Analysis Techniques: Key Components of Runtime 2

Database time ~89% of total runtime (1064 of 1162 seconds)

Ratio records selected / records transferred: 2.1


query performance

37


Performance Concerns: if not aggregates, then what?

Resource Constraints? CPU speed Number of CPUs Available memory I/O throughput, number of controllers

Database Statistics – Are they complete and up-to-date?

Use of OLAP Cache

Query Design – Start at summarized level, drill down for details?

Design Considerations InfoCube Partitioning MultiProvider Line Item Dimension ODS – InfoCube – Report to Report Interface

Web Applications Compression Precalculation

38


Agenda

Setting Up BW Statistics

39


Enable Capture of Statistical Performance Data

Choose Tools > BW Statistics for InfoProviders

Can be turned on/off for OLAP/WHM

You can delete old data from database tables

You can store new settings permanently

40


Customizing: Transfer Business Content DataSources

Where? Transaction SBIW

41



All Components Under “TCT” Must Be Selected for Transfer

Where? Transaction SBIW,

Transfer Business Content DataSources

42



Choose “Select Delta”, Then “Transfer DataSources

43


Replicate DataSources (Self Source System)

Where? Administrator Workbench > Modeling > Source Systems > Select Self Source System > Context Menu

44


Business Content Installation: Group Objects

Where? Administrator Workbench >

Business Content > Grouping Options

45


Business Content Installation: Select InfoProviders

Drag and Drop BW Statistics InfoProviders into Collected Objects

Workspace

46


Business Content Installation: Check & Install

Ensure That All Objects in Tree Are Selected For Installation

(or are already active), then Choose “Install”

47


Business Content Installation: Collect Object Superset

Repeat Object Grouping Steps, But Now Choose Grouping Option All Objects In Dataflow Before and After

48


Business Content Installation: Check Objects & Install

Spot Check Objects:

Expand Update Rules, then

Continue Expansion to InfoPackages

Ensure All Objects Are Selected for Installation

(or active)

Install

49


Post-Content Installation: Check InfoPackages

Where? Admin WB > Modeling >

InfoSources:

Check for Existence of InfoPackages

50


Post-Content Installation: Check Data Flow Diagram

Where? Admin WB > Modeling > InfoProvider > Technical Content > BW Statistics >

MultiProvider for BW Statistics > Context Menu > Show Data

Flow

51


Post-Content Installation: Check Data Flow Diagram52


BW Statistics Setup: Data Loads

Check delivered InfoPackage groups; Utilize and modify as needed. Consider building process chains to automate data loads.

InfoPackage Scheduler: perform data loads for all master data InfoSources under the Technical Content InfoArea and the BW Metadata InfoArea

InfoPackage Scheduler: Perform delta initializations for all transaction data InfoPackages under the Technical Content InfoArea

InfoPackage Scheduler: Schedule regular delta data loads for all transaction data InfoPackages under the Technical Content InfoArea

InfoPackage Scheduler: Schedule regular data loads for all master data InfoPackages under the Technical Content InfoArea and the BW Metadata InfoArea

Regularly monitor data loads and ensure timely data availability.

53


BW Statistics Setup: Assign Technical Content Role

The Technical Content Role (SAP_BWC_TCONT ) is activated via the BW statistics business content installation.

The delivered BW Statistics Workbook is (by default) contained within the Technical Content Role (SAP_BWC_TCONT ).

Use transaction PFCG to assign the Technical Content Role (SAP_BWC_TCONT) to any users who should have easy access to the BW Statistics Workbook.

Important OSS notes (BW statistics) :

422264, 309955, 551552

54


Important Resource

How-to-guide:

“How to Setup BW Statistics”:

Valid for versions 2.0B, 2.1C, 3.0B and 3.1Content

Available at http”//service.sap.com/BW > Services & Implementation > How to Guides > Guide list BW 3.0

55


Q&A

Questions?56

Documents

SAP BW Performance Monitoring with BW Statistics