尤尼佳02_howto_archive_in_bw.docVIP

How to… Archive in BW ASAP “How to…” Paper Applicable Releases: BW 3.0A November 2001 Business Scenario You have data in your system that you do not want to delete for good, instead, you want to move it away from your main data targets (InfoCubes and ODS Objects). You want to improve the load and query execution performance by decreasing the volume of data. In addition, you want to restrict system growth, and have decided to move some of the data onto a slower storage medium, which is also cheaper than the expensive, quickly accessible memory within your system. You may need to retrieve this data some time in the future and therefore, you think about archiving your data. Note Remarks for the archiving of InfoCubes with Non-cummulative key figures are provided in Appendix. Solution BW Archiving in 3.0 is the process of selectively writing the data of a data target to a file and subsequently deleting this data from the respective data target. This process is split in two parts, one job for writing and one job for deleting the data. Hence, the consistency of the archived data is guaranteed. No data will be deleted before not all archive files of the write job are verified, that is, they are accessible and complete. Archiving in BW uses the Archiving Development Kit (ADK). The ADK is well established in the R/3 environment. It has several beneficial features. Some of the BW relevant features of ADK are: Handling structural changes Since the ADK is storing metadata of the archived data as well as the data itself, it is capable of retrieving the archived data even after structural changes have been made. This data is not converted to the new structure, but simply displayed in the new structure. Platform independency The ADK can handle different code pages (ASCII, EBCDIC, UNICODE) and number formats. Data compression The archived data can be compressed up to 5 times of the original data volume. Archiving Information System (SAP-AS) The archived data can b