Improve Your System Performance by Archiving Data in BW: Part 2

  • by Gary Nolan, SAP BI Strategic Architect, Sapiex Associates LLC
  • April 15, 2006
When you need to retrieve archived data, follow this process to load it back into your BW system.
Key Concept
Archiving removes outdated data, but sometimes a need arises to analyze archived BW data and you must reload it back into the BW system. For example, your company archived and deleted order data from four years ago. The sales department now requests this data for new promotional analysis that it wants to perform. You cannot read this archived data directly into queries; instead, you must reload it back into BW and then analyze it in BW queries.

Once a BW system archives data, you may need to reload the archived data files back into the BW system because of legal or audit requirements. I’m going to walk you through the process you follow to reload BW archived data back into the BW source system where it originated. This data existed in a BW InfoProvider (InfoCube or ODS) and your company archived it to a file and deleted it from a BW source system.

The only two structures available for archiving are the InfoCube and ODS. Archiving is not available for master data or Persistent Staging Area (PSA) data. You can only reload BW data archived from the InfoCube or ODS back into BW.

I highly recommend that you not reload the archived data back into the original data target. For example, if you originally created an archived file from InfoCube A, you should not reload it back into InfoCube A. You should copy InfoCube A and create a new InfoCube B. You then can reload archived data into InfoCube B.

There are several reasons for this recommendation. The most important is that it allows the reloaded data to remain physically separate from any existing data. This allows for easier verification of the reloaded archive data because the data is isolated in its own InfoProvider. You also can combine reloaded data with current data via MultiProviders for better query performance because of the system’s parallel query processing functionality.

You should fully test the entire archival process in a development environment and then in the production environment. Therefore, you need to transport all objects that you created for this process using the BW transport functionality.

Gary Nolan

Gary Nolan is an SAP NetWeaver BW-certified consultant and author of Efficient SAP NetWeaver BW Implementation and Upgrade Guide and Efficient SAP NetWeaver BI Implementation and Project Management. Gary specializes in gathering and evaluating requirements, configuring SAP NetWeaver BW, and providing project management, performance management, and data architecture and data modeling expertise. A former platinum consultant with SAP America, Inc., Gary has more than 20 years of SAP experience, working with SAP NetWeaver BW since version 1.2B.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.