The Tip Doctor, Insider Learning Network
The SAP NetWeaver BW Nearline Storage (NLS) component was introduced in the initial SAP NetWeaver BW 7.0 release. A number of enterprises are already taking advantage of this feature, and their experiences have led to the identification of the following best practices for an Information Lifecycle Management (ILM) implementation.
1. Don’t wait to encounter database size issues before thinking about introducing an ILM strategy. Start early with a preventative approach rather than undertaking a more complex and expensive cure later on.
An ILM implementation has two main phases:
- The initial ILM data migration process
- The ILM steady state
The steady state is attained at the point when only the required data is kept online, which means that all static data has been moved to the NLS solution. During the initial ILM data migration process, an enterprise may have to migrate a large amount of data to catch up, which can have a major effect on the costs and time requirements of this operation. This also puts additional pressure on already constricted batch windows, thereby increasing the amount of time required to reach the steady state.
Frequently, ILM implementation projects do not allocate sufficient time for initial data migration, mainly because the amount of time required for data deletion and database reorganization is underestimated — this can actually represent up to 70% of the migration process. The longer the enterp
rise waits before implementing ILM, the more time is required to reach the steady state when pressure on the batch windows is eased considerably. So, the quicker and more aggressive the ILM implementation is, the sooner real benefits materialize.
This excerpt was taken from Richard Grondin’s “12 Best Practices for Information Lifecycle Management Using the NLS Interface” (BI Expert Update 2, 2010)