0

Proven Techniques for Improving Reporting and Analytics Performance Using SAP NetWeaver BW Accelerator Including BWA 7.2 new features Dr. Bjarne Berg Comerit Inc.
2011Wellesley Information Services. All rights reserved.

In This Session ...

Show what SAP NetWeaver BW Accelerator is and how it works Look what SAP BW Accelerator can and cannot do to optimize query and dashboard performance Explore how to plan and implement SAP BW Accelerator. Take a look at SAP BusinessObjects capabilities and the new SAP BusinessObjects Explorer options Examine performance benchmarks for SAP BW Accelerator Look at the future of the SAP NetWeaver Business Accelerator tool and the roadmap

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

Why In-memory processing?

Disk speed is growing slower than all other hardware components

Technology Drivers
1990 CPU 2010 Improvement

Architectural Drivers
1990 Disk-based data storage Simple consumption of apps (fat client UI, EDI) Generalpurpose, applicationagnostic database 2010 In-memory data stores Multi-channel UI, high event volume, cross industry value chains Applicationaware and intelligent data management

0.05
MIPS/$

253.31
MIPS/$

5066x 2502x

Memory

0.02
MB/$

50.15
MB/$

Addressable Memory Network Speed

216
100
Mbps

264
100
Gbps

248x
1000 x

Disk Data Transfer

5
MBPS

600
MBPS

Source: 1990 numbers SAP AG 2010 numbers, Dr. Berg

120x

Physical hard drive speeds only grew by 120 times 4 since 1990. All other hardware components grew faster.

In Memory Processing - General Highlights - BWA

3. Queries are routed to BWA by the Analytical engine

SAP BW
BI Analytical Engine 2. Indexes copied in to RAM on blades

InfoCubes
1. Indexing and compression stored on a file system

DSOs

In Memory Processing - Creating Indexes from external data

Using the Index Designer in Data Services, you can also index data from external data files and data bases. For BWA you should always have one 'spare' blade for failover. If a blade fails, the system can reload the indexes from the BWA file system (i.e. IBM's GPFS). It is important to note that the BO indexes are on dedicated blades.

3. Queries are routed to BWA by the Analytical engine

SAP BW
BI Analytical Engine 2. Indexes copied in to RAM on blades

InfoCubes
1. Indexing and compression stored on a file system

DSOs

Business Object Data Services

External data
Data Integrator

Index Designer

Files

Databases

How Does SAP BW Accelerator Work in Reality??

SAP BW Accelerator 7.0 performs aggregation and data selection for the query, all other processing is done by the BI analytical engine (aka as the OLAP processor).

Therefore, not all query processing will be dramatically faster

In SAP BW Accelerator 7.2 you can handle more of the analytics processing, such as top-5 products sales, which was previously done in the BI analytical engine SAP BW Accelerator is accessed by queries and also by any job the use the application programming interface (SAPRSDRI_INFOPROV_READ) or the data read transaction (LISTCUBE), when aggregate flag is selected or any of the OLAP interfaces to 3rd party tools
7

The New SAP Explorer and SAP BW Accelerator

The new SAP BusinessObjects Explorer (not SAP BEx) brings together inmemory processing SAP BW Accelerator with the SAP BusinessObjects business intelligence (BI) search engine Users can search & explore large volumes of enterprise data to answer on the fly questions, discover relationships, and uncover root cause All business users gain immediate insight without needing assistance from business analysts or IT. No training required

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

Compression and TREX The TREX engine is NOT the same as the traditional implementation of the search engine. BW Accelerator comes its own TREX engine that collects the data. During the index build, the data is also compressed using advanced mathematical methods. The result is therefore a much smaller sized index than the original InfoCube

10

The Three steps of InfoCube Index creation First master data is processed (Y, S and X) tables Second, the fact tables grouped and indexed. This occurs by merging the E and F tables into one F table prior to indexing it. This is done automatically and does not change the basic cube. Third, the dimension tables are indexed. This include all D-tables (potentially 16) The process starts with a database lock on each table. The next step is a data transfer to a temporary BWA file and transferring the data to BWA. The final step is to write the indexes to memory and activate it for queries.
11

The Rule of 50% and Impacts Buying hardware is not as easy as you may think. First you need to make space for temporary index files. The recommended size is about 50%. Second you need to have one fail-over blade in case of hardware issues.
Example-1: Your sizing program says you need 48Gb of memory You need 48GB + 48Gb for temp indexes and 48Gb failover = 144Gb (66.66% overhead) Example-2: Your sizing program says you need 192 Gb of memory You need 192GB + 192Gb for temp indexes and 48 Gb failover = 432Gb (44% overhead)
12

Performance is Near-Linear: Benchmarks

SAP BW Accelerators strength resides in its near-linear scalability Performance is measured in terms of:
1. BW Accelerator index creation time 2. Multi-user throughput per hour 3. Average report response time 4. Average number of records touched by each report SAP BW Accelerator currently reads data from InfoCubes. DSOs and InfoObjects are still read from base/physical tables (even when the InfoObject is indexed as part of master data).

13

BI Analytical Engines Query Executing Priorities

Information Broadcasting / Precalculation Information Broadcasting / Precalculation

Query Cache

Query Cache

Aggregates

SAP BW Accelerator

InfoProvider

Query Execution Without SAP NetWeaver BW Accelerator

Query Execution With SAP NetWeaver BW Accelerator

Aggregates can be replaced with SAP BW Accelerator, while the memory cache is still useful.

14

Query Performance Improvements - Real Example of 70 queries

The slowest queries that spent most of their time on the database side benefited the most Overall 36 of 70 queries were at least twice as fast. Before SAP BW Accelerator, the average query execution took 58.8 seconds; after SAP BW Accelerator the average query took 17.9 seconds (295% faster overall).

15
BI Accelerator (BWA) has been renamed to SAP BW Accelerator

Query Performance Improvements OVERALL

Query execution time before BI-A
10 9 8

Number of Queries

7 6 5 4 3 2 1 0 10 15 20 25 30 35 40 45 50 55 60 70 80 90 100 110 120 140 160 180 200 220 240 260

Seconds

The major improvement is to make query execution more predictable and overall faster

Query execution time after BI-A

25 20 15 10 5 0

10 15 20 25 30 35 40 45 50 55 60 70 80 90 100 110 120 140 160 180 200 220 240 260

16

HINT: BWA will not be used if a query, has a key figure set to NO1, NO2 or NOP, (no aggregation)
Seconds

Number of Queries

Workbook Performance Improvements with SAP BW Accelerator

Workbooks require embedding of JavaScripts; can contain multiple queries; and may have macros, lookups, and internal logic It is therefore hard to estimate the real performance benefits of implementing SAP BW Accelerator In this real example of 20 slow workbooks, the average performance improvement for workbooks was 363% faster

17

Performance Info SAP BW Accelerator Indexes Build Times

Creating new indexes (refreshes) can be time consuming. The build time depends on: a) The size of the records (length) b) The number of records c) The number of SAP BW Accelerator processors d) The network transfer speed In this example, 23 InfoCubes with over 232 million records were indexed in 90.56 minutes

On average, 2.56 million records per minute were indexed!

18

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

19

Most Customers Have Found SAP BW Accelerator Admin to Be Minimal

The Admin work is done through a single interface The admin interface is available under the transaction code RSDDBWAMON/ RSDDBIAMON Health checks for SAP BW Accelerator are available under the transaction code RSRV

Most companies plan for a maximum of 2-5 days of SAP BW Accelerator training. You need a maximum of 1-2 administrators (1 for backup).
20

RSDDBIAMON - BW Accelerator administrator tools:

Restart BIA server: restarts all the BI accelerator servers and services. Restart BIA Index Server: restart the index server. Reorganize BIA Landscape: If the BI accelerator server landscape is unevenly distributed, redistributes the loaded indexes on the BI accelerator servers. Rebuild BIA Indexes: If a check discovers inconsistencies in the indexes, delete and rebuild the BI accelerator indexes.
21

Selective Usage of BWA

You can turn-off the BW Accelerator usage for certain roles. This reduces the stress on the hardware for non-essential user. You can also turn-off the BWA uses for individual users in transaction code SU01

You can see if anyone is using the BWA indexes in the table RSDDSTATBIAUSE and some details are also available in RSRT after patch 16

22

RSDDBIAMON - BW Accelerator administrator tools and control

Connectivity checks Check if BW is still connected physically to the BW system System Check Checks if the blades and file system is operating normally Load Monitoring Keep track of performance of the load process (read, writes, compression and time spent.

You can turn off the BWA index query availability for Infocubes through the transaction RSDDBIAMON2

23

Health-Checks and Reconciliation

The SAP BW Accelerator interface allows you to compare the data in SAP BW vs. the indexes. This means that you can easily check if they are outdated (service pack 12
required)

Other tools include the ability to run queries to see if the numbers in the two databases match.

You can check your installation using the function module

'TREX_CHECK_BIA_INSTALLATION

or using the transaction code RSDDBIAMON

24

Proposals and Estimations

The Analysis and Repair options include proposals and time estimation tools that you may use. The interface can propose deltaindexes for periodic updates. You can estimate run-time of indexing the fact table of an InfoCube before you place it into a process chain or a manual job. You can estimate the memory needed before adding new records into memory.
You can use the ABAP program
ZZ_SET_QUERY_NOHPA_FLAG to turn off BWA access for single queries in the RSRREPDIR table
(SAP note: 1161525 for BWA7.0)

25

The SAP BW Accelerator Reset Button

The simple way to fix most issues is to delete all indexes and rebuild them during a weekend Think of this as the ultimate reset button. You can also rebuild master data indexes
In TREXADMIN you can see the number of records in the BWA indexed Infocube. 1. Select the RFC Server, Execute, 2. Click on tab Index Admin 3. For each InfoCube select BIA as the Index ID. The records are equal to the # of documents. 4. Estimations of this, based on statistics, are also available in: RSDDV- BIA Indexes SE16 - RSDDTREXDIR
26

Increasing Index Creation Performance

1. To increase index creation performance, you can change the global parameters in BWA. 2. Pay particularly attention to the number of parallel processes available (max 10 per available physical processors) 3. Make sure the memory buffers are set large enough to accommodate large infocubes. 4. Review consistency check recommendations in SAP notes: 1052941 and 1161967

You can check global parameters in RSRV You can change global parameters in RSBATCH and RSDDBIAMON

27

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

28

Planning a 6 -weeks SAP BW Accelerator implementation A BWA Project can be completed in 6-weeks. However, due to hardware lead-times (normally 4-6 weeks), most project should plan a 12 weeks duration. The time waiting on hardware should be used on performance tuning of existing queries and dashboards In the this section we will look at the major tasks of implementing a BWA solution

29

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

During project start up, make sure you have someone from basis, network, physical hardware and system admin available to coordinate schedules, access and resources 30

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

Not all InfoCubes needs to be indexed. Use the Earlywatch reports to find the slow performing queries that have a significant number of users and are accessed at a high frequency.

31

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

Sizing is important to determine the overall system hardware needed. You cannot use the size of the InfoCubes, since the TREX indexing also uses compression to reduce overall size.

32

Sizing Is Critical, but Good Tools Are Available

SAP has integrated key sizing parameters for SAP BW Accelerator in the new Quick Sizer. You can give it a try at: http://service.sap.com/quicksizer (requires login credentials for the SAP Service Marketplace) Customer with existing BI systems and data loaded can get good sizing and 33 compression estimates by running the SAP program available in SAP Note: 917803

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

You should plan for at least one extra blade per environment in-case the server blade fails (you can rebuild indexes to this blade). You also contingency plans in-case the BWA indexes becomes unavailable.

34

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

As soon as you have approvals, contact the vendor and place the BWA order. These are often built-to-order and lead-times for delivery is frequently 4-6 weeks.

35

Some Hardware Options

Operating Systems and Storage SUSE Linux 64-bit, Intel based Memory based and file storage (no database for Accelerator) Available Hardware Platforms HP (HP ProLiant and HP StorageWorks) IBM (IBM Blade Center and IBM Total Storage) Fujitsu Siemens (FSC Blade Server and EMC Storage) SUN Microsystems (SUN Blade Server and StorageTek)

The hardware implementation is done by the vendors. Be prepared for lead times on delivery of large systems (made-to-order is common).
36

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

BWA works primarily on database fetch operations, processes in the BI analytical engine is still performed. You should therefore also tune these and redesign poorly performing queries before BWA is implemented 37

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

BWA hardware is simple to install. The trick is to have the right people involved & make sure that the data traffic between the database server and the BWA server is not using old data networks with slow routers and shared switches.

38

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

You need to plan for 2 system admin to be trained. One for the daily work and one for backup during vacations and travel.
39

Training for SAP BW Accelerator

Reference BW-310 BW-305 BW-350 BW-360 BW-361 BW-365 SAP-330

Title Intro to SAP BI BI Reporting and Analysis BI Data Acquisition BW Performance & Admin BW Accelerator BW Authorizations BW Modeling

Audience All Query developers ETL developers System admin System admin System admin BI developers

SAP BW Accelerator training is included in the SAP courses: BW-310, BW-360 and in the online course BW361

In the past, SAP has also offered a 2 day workshop called BI Upgrade & Accelerator (WNASAP BW Accelerator)

40

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

Build a small sub-set of indexes and test them before you spend time on the complete system. This will help determine how long it will take to create indexes and what performance increase you will obtain.

41

Planning an SAP BW Accelerator implementation

Weeks

BIA Implementation Plan

Project start up BW implementation review and ranking of InfoCubes for indexing Review physical hardware infrastructure and network access Size the BIA using program in note: 917803 Plan for fail-over, disaster recovery and backup Approvals and vendor selection Contact vendor and place Purchase order Collect benchmarks for current performance and targets Execute performance tuning of queries Document improvements Install hardware and connectivity Test connectivity and perform readiness assessment Training for 2 system admins Create first indexes and test functionality Make enhancements and change scope as needed (i.e. more infocubes) Create all planned indexes Execute system test Design and implement updated process chains Collect benchmarks for current performance and targets Document results and close project

9 10 11 12

Test the overall solution over a weekend and compare the benchmarks against those you had in week 3 to document success and possible bottlenecks. Integrate the index creation times into the existing process chains and monitor impacts.

42

Team Organization
1. Create a small team of three people dedicated to the SAP BW Accelerator project supported by one Basis person and the rest of the BW team Hardware team members supported by the vendor should also be involved in a part-time capacity Overall the SAP BW Accelerator effort should be combined with a performance tuning project that also includes building of aggregates, caching, and query redesigns

2.

3.

43

Testing
1. Make sure you identify real benefits and benchmark with pre- and post-performance after SAP BW Accelerator is implemented

2.

This requires that all critical performance data is captured before SAP BW Accelerator is installed

3.

You should document the post performance and build times as early as possible so that you know what the performance of complex dashboards will be and how the indexing will fit into existing process chains

You can see what InfoCubes are indexed by going to RSDDV and press the button "BIA Indexes.
44

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

45

The New SAP BW 7.2 Features Modeling in BWA

In BWA 7.2 you can complete many of the joins and the aggregation that previously was conducted in the BI Analyitcal engine, and was therefore hard to performance tune. It also reduces the data being transferred to the app-server and therefore are much faster as well.

Image source: SAP AG, 2011, SDN

The New SAP BW 7.2 Features Faster Performance

Image source: SAP AG, 2011, SDN

The major benefit of the BWA7.2 is that you can move more of the calculation over to the accelerator and materialize the result inmemory. This improves the reads and calculations in the OLAP/ BI analytical engine on the BW side is substantially reduced. The following calculations is now included: SUM MIN MAX CNT (count all detailed values) CN0 (Count all values not zero or null) AVG (average) AV0 (Average for all values not zero or null)

Pre-requisites BWA 7.2

FOR BO EXPLORER - BWA needs to be upgraded to BWA 7.20 - BW should be upgraded to minimum BW 7.0.1 EnhPk 1; SPS 5
(Source SAP AG BWA 7.2 Installation guide, Dec. 2010 and OSS notes:1392524 and 1148111)

SAP Technology RIG Recommendations: - If the system is on SAP NetWeaver BW 7.0 or 7.0 EhP1, then use BW Accelerator 7.0
- If the system is on SAP NetWeaver BW 7.0 EhP1 SPS 5 or higher AND you are using BusinessObject Explorer (accelerated version), then use BW Accelerator 7.20 - If the system is on SAP NetWeaver BW 7.3, then use BW Accelerator 7.20
(Source Marc Bernard, SAP AG, 2011)

48

The SAP BW 7.2 Limitations and Query Settings

There are still some limitations. For example you cannot use the exception aggregation for single key figures in BWA if it uses:
1) 2) 3) 4) 5) Virtual key figures Conversion before aggregation Formula calculation before aggregation Non-cumulative key figures Key figures with elimination of internal business volume

You also get more detailed control on each query as to how it reads the BWA. Think of it as similar to Query read modes
(more details at SDN : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/ uuid/70950003-f7ef-2d10-b1bcee483800b25c?QuickLink=index&overridelayout=true

The New SAP BW 7.2 Performance example

Queries with large OLAP processes, such as average and counts benefits the most from the new BWA 7.2 system. SAP has published the following performance example:

90-95% FASTER!!

What Well Cover

What is SAP BW Accelerator? Performance benchmarks Managing and administrating SAP BW Accelerator Planning an SAP BW Accelerator implementation BWA 7.2 Wrap-up

51

SAP BW Accelerator is becoming mainstream

Some of SAP reference clients
(source: SAP AG, 2011)

SAP BW Accelerator is no longer something exotic

Nike

Many of the large BI systems have already implemented SAP BW Accelerator and many more projects are under way in Europe and in the Americas

Once you exceed a few hundred critical users and/or 3-4 TB of data, you should seriously consider SAP BW Accelerator

Resources

BWA forum:  https://forums.sdn.sap.com/forum.jspa?forumID=273 SAP BW Accelerator nerve center SAP White papers, demos and technical information  https://www.sdn.sap.com/irj/sdn/BWA What is New in SAP BW 7.3 and BWA 7.2 SDN presentation  http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7095000 3-f7ef-2d10-b1bc-ee483800b25c

53

7 Key Points to Take Home

Plan to order hardware early Lead times can be long Create benchmarks for workbooks, queries, and cockpits to document success Be realistic, not all queries will benefit equally from SAP BW Accelerator Involve your Basis team and environment management team early Plan for testing and gradual rollout of SAP BW Accelerator to key users Make sure failovers and spare blades are part of your hardware sizing Create a small dedicated team with access to external expertise as needed Perform query tuning and potential redesign as part of a larger system performance tuning effort
54

Your Turn!

How to contact me: Dr. Bjarne Berg bberg@comeritinc.com

55

Disclaimer
SAP, R/3, mySAP, mySAP.com, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP.

56