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.

the F- fact table, the E- fact table reference point can be accessed directly <strong>for</strong><br />

current data, thus improving query per<strong>for</strong>mance.<br />

There is one exception when <strong>SAP</strong> compression can be omitted. This is the<br />

case when you are <strong>using</strong> the <strong>SAP</strong> <strong>BI</strong>A and when the compression ratio is less<br />

than 1.5.<br />

7. Use fast deletion of table partitions.<br />

Apply <strong>SAP</strong> note 894045 to activate the fast deletion of table partitions <strong>for</strong><br />

partitioned PSA and F- fact tables.<br />

8. Partition E-Fact and F- fact tables.<br />

The E- fact table (result of <strong>SAP</strong> compression) can be partitioned via <strong>SAP</strong><br />

cube maintenance, which provides greater opportunity <strong>for</strong> improved query<br />

per<strong>for</strong>mance and elapsed time, and also potential reduction in operational<br />

costs.<br />

Partitioning the E- fact table increases the opportunity <strong>for</strong> <strong>DB2</strong> parallelism,<br />

which can significantly reduce the query elapsed time. Similarly, queries with<br />

time-based filtering will be able to eliminate unnecessary partitions from being<br />

accessed regardless of the filtering dimensions or indexes chosen <strong>for</strong> fact<br />

table access. These two benefits also result in greater access path stability<br />

<strong>for</strong> queries against the InfoCube.<br />

The F- fact table will be automatically partitioned by request by setting a<br />

RSADMIN parameter. In addition to improving query per<strong>for</strong>mance, this<br />

significantly speeds up the deletion of a request and the RUNSTATS. Details<br />

are in <strong>SAP</strong> note 860830.<br />

An additional benefit of partitioning is the ability <strong>for</strong> partition level operations<br />

such as COPY utility, REORG, or RUNSTATS to be invoked by the DBA.<br />

With time-based partitions, historical partitions do not require further<br />

REORG/RUNSTATS because their data will not change over time. An<br />

increase in E- fact table size should not result in a significant increase in<br />

operational maintenance costs.<br />

For these reasons we recommend partitioning the E- fact tables and <strong>using</strong><br />

InfoCube compression.<br />

9. Use <strong>DB2</strong> HW compression.<br />

<strong>DB2</strong> hardware compression is one of the strengths that differentiates <strong>DB2</strong> on<br />

System z from other plat<strong>for</strong>ms. Compression rates of 70% and greater are<br />

possible <strong>for</strong> large <strong>SAP</strong> <strong>BI</strong> objects, such as fact tables, data store objects, and<br />

large aggregates. The four main benefits of compression include:<br />

– Reduced disk space<br />

– Improved elapsed time <strong>for</strong> sequential processing (<strong>for</strong> example, queries,<br />

copy utility)<br />

32 <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!