Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks
Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks
Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Furthermore, the <strong>SAP</strong> <strong>BI</strong> application is different from other <strong>SAP</strong> modules,<br />
especially regarding the use of a database. Thus, it is important to look into the<br />
per<strong>for</strong>mance of <strong>SAP</strong> <strong>BI</strong> with <strong>DB2</strong> v9.1 <strong>for</strong> z/<strong>OS</strong>, as this <strong>Redbooks</strong> publication<br />
does.<br />
1.2 The audience <strong>for</strong> this <strong>IBM</strong> <strong>Redbooks</strong> publication<br />
The goals of this book are to give an integrated view of key <strong>SAP</strong> <strong>BI</strong> and <strong>DB2</strong> 9 <strong>for</strong><br />
z/<strong>OS</strong> per<strong>for</strong>mance indicators and to offer a process <strong>for</strong> <strong>using</strong> them together.<br />
The audience <strong>for</strong> this document includes both System z <strong>DB2</strong> DBAs and <strong>SAP</strong> <strong>BI</strong><br />
Basis Administrators responsible <strong>for</strong> administering <strong>SAP</strong> <strong>BI</strong> on System z <strong>DB2</strong><br />
production systems, and <strong>SAP</strong> <strong>BI</strong> functional architects responsible <strong>for</strong> designing<br />
the <strong>BI</strong> system’s InfoCubes, Aggregates, and Data Storage Objects (DSO)<br />
objects.<br />
Note: It is important that there is early cooperation between the functional<br />
designers and the technical implementation specialists. All those listed will<br />
benefit from reading this book.<br />
The <strong>SAP</strong> <strong>BI</strong> solution is not the only <strong>DB2</strong> 9 solution within a company. Most<br />
companies have different early systems running on System z. For the <strong>IBM</strong><br />
mainframe infrastructure, a support organization exists within the company. Most<br />
groups tend to work independently from each other.<br />
With <strong>SAP</strong> <strong>BI</strong> on System z, as with other <strong>SAP</strong> solutions on the <strong>IBM</strong> mainframe,<br />
you must communicate with all groups that are responsible <strong>for</strong> the operation of<br />
the <strong>SAP</strong> solution. Ideally there should be a person in your organization who<br />
bridges the gap between the different support groups — the user acceptance<br />
and per<strong>for</strong>mance of your <strong>SAP</strong> solution will benefit.<br />
The focus of this <strong>IBM</strong> <strong>Redbooks</strong> publication is on per<strong>for</strong>mance problems: how to<br />
avoid them, how to troubleshoot per<strong>for</strong>mance problems that cannot be avoided,<br />
and how to solve the problems once identified. Most per<strong>for</strong>mance problems can<br />
be avoided if <strong>for</strong>esight is used and design decisions take certain issues into<br />
consideration.<br />
This book can also be used <strong>for</strong> decisions concerning <strong>SAP</strong> on System z, as<br />
discussed in Chapter 4, “Benefits of <strong>DB2</strong> 9 <strong>for</strong> <strong>SAP</strong> <strong>BI</strong>” on page 35. Key areas we<br />
cover are load per<strong>for</strong>mance, query per<strong>for</strong>mance, per<strong>for</strong>mance during<br />
administration processing, and storage reduction.<br />
Chapter 1. Introduction 3
Change language