sap bw performance monitoring with bw statistics.ppt

Know How Network:SAP BW PerformanceMonitoring with BWStatistics

Ron SilbersteinPlatinum ConsultantNetweaver RIG USSAP 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:MultiCubeInfoCubesQueriesWorkbook (New one as of BW 2.0B)InfoSourcesTransfer Structures, Transfer Rules, Update RulesInfoPackages, InfoPackage GroupsRole

4


BW Statistics: Facts (continued)

Maintenance requires scheduling data loads and monitoringDelta load functionality deliveredTransaction DataMaster Data

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

ST03 > Expert Mode > BW system loadTable RSDDSTATFunction Module RSDDCVER_RFC_BW_STATISTICS

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

Object metadata of BW Statistics is transportable

5


BW StatisticsMultiProvider

QueriesQueries

aggregatesaggregates

warehousemanagementwarehouse

management

Table RSDDSTAT

Analysis byqueries

(in workbooks)

Table RSDDSTATAGGR

Table RSDDSTATWHM

Info-SourceInfo-

Source

Turn on/off loggingfor 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

ChooseTools > BWStatistics forInfoProviders

Can beturned on/offforOLAP/WHM

You can deleteold data fromdatabasetables

You canstore newsettingspermanently

7


Consequences

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

Tables, which are filledby ‚OLAP‘:

RSDDSTAT

RSDDSTATAGGR

RSDDSTATAGGRDEF

Tables, which are filledby ‚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 RuntimeUser, query, # of navigations, components of runtime

Use of OLAP by Date

Use of OLAP according to time of day

Mean Time Per QueryMean 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 informationfrom 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 inTotal Run Time per

InfoCube

High % DBTime

High ratio:Selected /

transferredrecords

Expert Mode!

20


In transaction SE16, display table RSDDSTAT

Using Table RSDDSTAT

INFOCUBEQUERYIDQRUNTIMECATEGORYQNAVSTEPQDBSELQDBTRANSQTIMEDBSTARTTIME

Width of output listMaximum no. of hits

Number of entries

totototototototo

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 displayquery names

22


Important Fields in Table RSDDSTAT (1)

Query name Runtime Category Database time Records selected onthe database

Recordstransferred

from thedatabase tothe OLAP

23


Agenda

Detecting Optimization Potential

24


Analyzing Reporting Performance Issues

Building Aggregates:

Primary technique for tuning reporting performanceAnalyze 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 InfoCubeswith queries having the highest runtimes

27


Front-end

Database Server

Stastistics for Queries

Application Server

InfoCubeData

Queryexecution

BExAnalyzer

WebBrowser

OLAPprocessor

Front-endtime?

OLAPtime?

Databasetime?Number of rows

selected on thedatabase?

Number of rowstransferred to the

applicationserver?

Amount ofdata

transferred tothe front-end?

1

2

3

Aggregates

28


Indicators That Aggregates Will Help

Infocube Number of recordsread on thedatabase (QDBSEL)

Recordstransferred afterbeingsummarized onthe 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 forqueries > 30% oftotal query runtime

One Key Indicator:

Ratio records selected / records transferred> 10

Look for many more recordsselected than necessary!

29

AND


Analysis of BW Statistics at InfoCube Level (1)

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

Ratio recordsselected /recordstransferred: 24

Aggregates will probablyimprove query performance

30


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


Aggregates will not improvequery performance

Analysis of BW Statistics at InfoCube Level (2)31


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

Aggregates will not improve

query performance

Ratio recordsselected /recordstransferred: 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 recordsread on thedatabase (QDBSEL)

Recordstransferred afterbeingsummarized onthe 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 forqueries > 30% oftotal query runtime

One Key Indicator:

Ratio records selected / records transferred> 10

Look for many more recordsselected than necessary!

29

AND


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

Using BW Statistics: Find Queries for Analysis35


Utilizing OLAP per Query Database time ~60% oftotal runtime (2.798 of4.685 seconds)


Aggregates will improvequery performance

Analysis Techniques: Key Components of Runtime 136


Analysis Techniques: Key Components of Runtime 2

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

Ratio recordsselected /recordstransferred: 2.1

Aggregates will not improvequery performance

37


Performance Concerns: if not aggregates, then what?

Resource Constraints?CPU speedNumber of CPUsAvailable memoryI/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 ConsiderationsInfoCube PartitioningMultiProviderLine Item DimensionODS – InfoCube – Report to Report Interface

Web ApplicationsCompressionPrecalculation

38


Agenda

Setting Up BW Statistics

39


Enable Capture of Statistical Performance Data

ChooseTools > BWStatistics forInfoProviders

Can beturned on/offforOLAP/WHM

You can deleteold data fromdatabasetables

You canstore newsettingspermanently

40


Customizing: Transfer Business ContentDataSources

Where? Transaction SBIW

41


Customizing: Transfer Business ContentDataSources

All Components Under “TCT” Must Be Selected for Transfer

Where? Transaction SBIW,Transfer Business Content DataSources

42


Customizing: Transfer Business Content DataSources

Choose “Select Delta”, Then “Transfer DataSources

43


Replicate DataSources (Self Source System)

Where? Administrator Workbench > Modeling > SourceSystems > 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 BWStatistics InfoProvidersinto 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 ObjectSuperset

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

48


Business Content Installation: Check Objects &Install

Spot Check Objects:Expand Update

Rules, thenContinue Expansion

to InfoPackages

Ensure All Objects AreSelected 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 > TechnicalContent > 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 dataInfoSources under the Technical Content InfoArea and the BW MetadataInfoArea

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

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

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

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 viathe BW statistics business contentinstallation.

The delivered BW StatisticsWorkbook is (by default) containedwithin the Technical Content Role(SAP_BWC_TCONT ).

Use transaction PFCG to assign theTechnical Content Role(SAP_BWC_TCONT) to any users whoshould have easy access to the BWStatistics 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


No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software componentsof other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, andOS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix SoftwareIncorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® andother Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other productsmentioned are trademarks or registered trademarks of their respective companies.

Copyright 2003 SAP AG. All rights reserved

sap bw performance monitoring with bw statistics.ppt

Documents