SAP Data Archiving

I only have a small SAP database – do I need to archive data?

If you have a relatively small SAP database (e.g. 200 GB) and it’s growing by less than 2% a month, archiving is not necessary at present.

If you have a larger database (e.g. 500 GB), that’s growing by 2%+ a month, there will be financial and system benefits to archiving, so we would highly recommend it.

It’s worth remembering that even a small database will reach a point at which it will be beneficial to control growth through archiving.

Find out more about SAP data archiving.

Storage hardware is cheaper now, so why not buy more storage, instead of archiving?

Buying more disc storage may solve your immediate problem. However it is not a viable long-term solution. Problems can arise with:

Hardware and system migration

A UK telecoms company had an 8TB database. They wanted to refresh hardware and move from Informix to Oracle. To move 8TB of data would take four to five days. This was not feasible as the business could not be down for that long. By archiving they drastically reduced the database down to about 3TB.

Data recovery

Large databases are also problematic for data recovery. We have worked with a customer who had 27TB of data in Oracle. To recover their data would take an estimated 3.5 days – which is totally unacceptable for a 24/7 operation.

Find out more about SAP data archiving.

Does data archiving make it difficult for users to access data?

No, not at all.

For most modules of SAP, such as FICO, MM and SD, users will not notice any difference when accessing archived data.

The only limitation is users will not be able to edit archived data, as it is stored in a read-only format.

For some SAP modules, like Project System, archived data may be viewed in a different format.

Find out more about SAP data archiving.

I’m upgrading to SAP ECC 6.0. Can I manage a data archiving project at the same time?

Yes! If you’re upgrading from R/3 4.6 or 4.7 to ECC 6.0 then archiving should be a key part of the project.

Upgrading to ECC 6.0 will increase your disc storage by 15% – 25%.  Running a concurrent data archiving project has dual benefits:

  1. Stabilising storage
  2. Quicker upgrade time

Our customers have reduced the time to convert to ECC 6.0 and Unicode by 25%, by also running an archiving project.

Find out more about SAP data archiving.

We’ve only been running SAP for a couple of years – do we need to archive yet?

The earlier you start archiving the better. The longer you leave it, the more difficult it becomes.

Unfortunately, only around one in six SAP customers archive from day one.

Benefits of archiving from day one (or as early as possible) include:

  • The people who configured SAP are available to provide information about the system design
  • Database growth and performance can be stabilised from day one.

Find out more about SAP data archiving.

How long does an archiving project take?

An archiving project runs exactly the same as any other SAP project:

  • Blueprint phase – 20-30 days (approximately)
  • Realisation phase – 15 days per module (approximately)

So for a project, archiving from, say, SAP FICO, MM and SD, total days will be between 65 and 75 over a six-month period.

Find out more about SAP data archiving.

What is SAP Data Archiving?

SAP data archiving is a decongestion process used to remove large volumes of data, no longer needed, from your live SAP database.

Archived data is moved to a more cost effective storage tier in a format that meets SAP best practice and allows for data retrieval and analysis.

We’ve helped over 500 SAP customers to identify data for archiving or deletion and supported them to complete a SAP data archiving project.

Find out more about SAP data archiving.

What is a SAP Archiving Object?

An Archiving Object specifies which data is to be archived and how. It directs SAP’s archiving system to the correct tables associated with a specific Business Object.

The Archiving Object name can be ten characters long and they are defined by the transaction AOBJ.

How do you identify a SAP Archiving Object?

Transaction DB15 is used to identify the Archive Objects. If you know the database tables or Archiving Object it displays a list of associated database tables for that particular Archiving Object.

Transaction DB02 is used to identify tables with high growth in data volumes. It compares the table size after archiving, thus monitoring data growth.

Transaction TAANA is used to identify the appropriate Archiving Object when a table has more than one archiving object.

PII Privacy Policy | Privacy Policy | © Copyright 2017 Proceed Group | Web design by Shaun Power Design