Why regularily archiving static data right now ? Why tracking unwanted data ?
- It is a good practice to keep the database at a manageable size and optimize performances.
- In a Mature SAP systems (that have behave with huge volumes of data, amassed over several years), enhancing the landscape with additional hardware of is only a short term solution.
- Going to work for so long (think ticking performance time bomb).
- Unchecked database growth can suddenly and dramatically increase batch response times, with unacceptable user response times following soon after.
- There is a clear and compelling ROI in terms of saved storage costs – that’s quite apart from the productivity savings and risk avoidance due to improved performance.
- SAP ILM (Information Lifecycle Management) makes possible to comply with SarbOx, FDA, Germany’s GDPdU, the UK’s FSA, regulations governing how long you have to retain data are not going away. The financial penalties for non-compliance are severe. Archiving as part of an ILM approach gives you unprecedented control over data retention and destruction and legal hold.
Just to underline archiving delivery, here are of some of the benefits realized by a company after introducing archiving :
- Database growth rate reduced from 120GB a month to a more manageable 50GB per month.
- The Materials Requirements Planning (MRP) runtime was reduced from 1 hour to just 20 minutes.
- Average interactive response time was improved from 1.2 sec to 0.7 sec (SAP recommends responses below 1 sec).
- No more ABAP dumps caused by performance issues (compared with five ABAP dumps per day before introducing archiving).
- The problem of lengthy backup times (backups taking 16 hours and impacting operations) was eliminated.
In case archiving is your objectives, Let’s take good practices :
Start archiving as soon as possible after a new SAP system implementation. This is recommended by SAP in order to start into good housekeeping habits, to keep system performance at optimum levels and to prevent unnecessary storage cost increases later.
Consider archiving before business productivity starts to be affected: Catch any performance problems warning signs that could raise: slower or erratic batch response times, a degradation in online response times or an increase in the number of query timeouts.
Reassure end users in the business that today’s archives are online, and archived data is accessible from the SAP application, so end users will see little difference. It’s just that the data is read-only, and is held in a compressed state on low-cost storage hardware.
Together with the business, a retention strategy must be defined: how long do different types of data need to be retained online? Which data can be deleted? Which needs to be archived and at what point in the future can it be removed from the archive? Buy-in from the business is essential so make sure you explain the benefits: better system performance for them and ultimately improved productivity and customer service.
Do analyze your SAP database before you begin. There are more than 100,000 tables in the SAP software: Prioritize!
Once you have delivered your first ‘quick wins’ and demonstrated the benefits to your business, undertake another health check to help assess where your next set of savings can be made.
In addition to an SAP-certified content server you will need specialist archiving skills to help you build, test and deploy your archiving strategy. Use archiving experts to guide you in choosing the correct archiving objects and customizing them, to work with your SAP system.
More than just data on your archiving system, you will be able to archive documents from the SAP spool and scanned, inbound documents too. This will free up additional database space and provide convenient long-term access to print lists and other key documents.