As you use your SAP system, your business processes generate masses of transactional data. This data fills your database tables and ultimately slows down SAP access to the more recent data that you need in your day-to-day job. Data which no longer needs to be referenced frequently should actually be moved out of your transactional SAP system into another repository – one where it will not slow down your normal SAP use but where it is still available should it need be accessed. This process is called data archiving.

At sidADM we recommend that your procedures for data archiving be defined as part of your SAP project implementation. More usually, however, the project is only taken up when the user base has already noticed that the system has grown sluggish over time.

Many customers choose to remedy SAP performance issues by increasing server resources - this only ever acts as a temporary fix as the ever-increasing data burden will eventually consume even the new resource. The implementation of a good archiving strategy will reap much more tangible and long-term benefits.

Page 1 of 2 | Next page ›