07.02.2013 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.1 Load PSA<br />

In this section we discuss the best practices <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> on <strong>DB2</strong> 9 <strong>for</strong> z/<strong>OS</strong> <strong>for</strong><br />

loading data into the PSA as part of the regular data loads into the <strong>SAP</strong> <strong>BI</strong><br />

system. We discuss techniques that can be employed to ensure that the PSA is<br />

managed efficiently. We also discuss techniques that will optimize data loading<br />

into the PSA as part of the data load into the <strong>SAP</strong> <strong>BI</strong> data targets.<br />

The source systems store logically dependent data in the <strong>for</strong>m of DataSources.<br />

Using the DataSources, the data is extracted and transferred to the <strong>SAP</strong> <strong>BI</strong><br />

system. In an <strong>SAP</strong> <strong>BI</strong> system, the PSA is used as the input storage, which stores<br />

the data in unchanged <strong>for</strong>m. This means that if the data in the source system is<br />

not consistent or contains errors, the data in the PSA is not error free.<br />

The basic role of the PSA is to provide a quality check of the input data coming<br />

from the source system. Another role of the PSA is to separate the loading<br />

process into <strong>SAP</strong> <strong>BI</strong> from the follow-on processes like data analysis and queries.<br />

Based on this separation, the loading per<strong>for</strong>mance can be tuned independently<br />

from other <strong>SAP</strong> <strong>BI</strong> activities.<br />

The usage of the PSA <strong>for</strong> loading into the <strong>SAP</strong> <strong>BI</strong> system is optional, but <strong>SAP</strong><br />

strongly recommends it from the <strong>SAP</strong> <strong>BI</strong> point of view.<br />

For the <strong>SAP</strong> <strong>BI</strong> 7.0 Data Update, <strong>SAP</strong> <strong>BI</strong> provides the following processing<br />

options:<br />

► Only PSAData is just written to the PSA and is not transferred or updated to<br />

additional data targets (<strong>for</strong> example, InfoCube, DSO).<br />

Defining the maximum number of processes in the source system influences<br />

the target system processes as well and improves the load per<strong>for</strong>mance.<br />

► PSA and then data targets<br />

Each data package is written to the PSA. The same process writes the data<br />

package to the data target after the PSA is updated successfully. Updating<br />

the data is provided serially, packet by packet.<br />

► PSA and data targets in parallel<br />

If the data package is successfully loaded into the PSA, a second process<br />

writes the data into the data targets, while the other data package, if any, is<br />

being loaded to PSA.<br />

56 <strong>Best</strong> <strong>Practices</strong> <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> <strong>using</strong> <strong>DB2</strong> 9 <strong>for</strong> z/<strong>OS</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!