Johns Hopkins University Data Archiving from Start to Finish

PublicSector_color

Running SAP systems since 1997, Johns Hopkins University had never archived any data. When performance issues started impacting their users, the University was told that that they should consider archiving. Some of the challenges the University faced were:

  • Too many records in the tables
  • Queries on transactional data were slow
  • System administration was taking too long and costs were too high
  • Storage needs and costs were increasing
  • Starting to see system performance degradation
  • Unique data issues in ECC, BW, and SRM systems
Solution The University developed an Information Lifecycle Management strategy, which defined the policies, processes and tools for data and information from conception to destruction. They turned to Dolphin to help them with the project which included:
  • User friendly access to archived data
  • Transparent access to archived data
  • Archiving in ECC, BW and SRM
  • Ability to retrieve archived workflows with the documents
  • Defined residency and retention periods based on the type data
  • Ability to perform ad hoc queries
Results Johns Hopkins continues to see success with their archiving project, which was rolled out in phases, gradually adding more arching objects. The University is especially pleased that the end users have been able to adapt to the new system so quickly and with very little training. The project provides:
  • Reduced DB size
  • Dramatically reduced the DB rate of growth
  • Additional archive objects added easily
  • 30% reduction in table size on average
  • Greater than 350M records archived and growing
  • End users satisfied and have had no problems accessing data

Back to Resource Library

Johns Hopkins University Data Archiving from Start to Finish

Running SAP systems since 1997, Johns Hopkins University had never archived any data. When performance issues started impacting their users, the University was told that that they should consider archiving. Some of the challenges the University faced were:

  • Too many records in the tables
  • Queries on transactional data were slow
  • System administration was taking too long and costs were too high
  • Storage needs and costs were increasing
  • Starting to see system performance degradation
  • Unique data issues in ECC, BW, and SRM systems

Solution

The University developed an Information Lifecycle Management strategy, which defined the policies, processes and tools for data and information from conception to destruction. They turned to Dolphin to help them with the project which included:

  • User friendly access to archived data
  • Transparent access to archived data
  • Archiving in ECC, BW and SRM
  • Ability to retrieve archived workflows with the documents
  • Defined residency and retention periods based on the type data
  • Ability to perform ad hoc queries

Results

Johns Hopkins continues to see success with their archiving project, which was rolled out in phases, gradually adding more arching objects. The University is especially pleased that the end users have been able to adapt to the new system so quickly and with very little training. The project provides:

  • Reduced DB size
  • Dramatically reduced the DB rate of growth
  • Additional archive objects added easily
  • 30% reduction in table size on average
  • Greater than 350M records archived and growing
  • End users satisfied and have had no problems accessing data