SAP Bank Analyzer Migration to SAP HANA – Progress Report

Recently, we finalized the migration of the SAP Analytical Banking platform to SAP HANA successfully together with our customer. Saying that SAP HANA is just a new or different database and you only have to exchange the SAP database server with the SAP HANA database server would be quite naive. Afterwards just a few configuration settings et voilá the SAP applications achieve high performance on SAP HANA. But as I said this is just the naive theory. Even though the above outlined goal of high performance processing on SAP HANA was successful, it has been a long way to reach this goal. Following the progress report regarding the migration or "HANA Migration Best Practices"

Progress Report

Long-term preparation
The SAP HANA migration has to be integrated into the existing release planning. The punctual supply of the new hardware for the sandbox as well as for the development, integration and productive systems is very important and you should plan a lead time accordingly.

Migration is not entirely an IT project
A migration project means team work and of course it needs the support of the IT department, but also from the specialist departments. Good cooperation between the departments, but also the regression tests’ goals should be coordinated at an early stage and be considered in the overall planning.

Commitment of experienced specialists
The SAP application environment is broadly diversified. Several applications have already been HANA ready for years, others only recently. Our project was kind of a “maiden voyage”, which means that our project is the first that migrated the appropriate module of the SAP Analytical Banking Suite to SAP HANA. Therefore, it was highly advisable to involve SAP from the beginning of the project. This especially accelerates the tracking, the handling of incidents and the help from SAP.

Little helpers
Now something for the techies: Where SAP standard sometimes reaches its limits our technical experts developed “best practice solutions”. This enabled top performance in regards to performance, scaling and optimized use of resources. Some of these little helpers are:

Optimization of SAP BA and HANA DB settings

  • Avoidance of multi-column indices and creation of single-column indices, table partitioning
  • Adjustments to developments and the use of cache methods to avoid single selects on the HANA database
  • Optimization of process settings (e.g. parallelization, package size)
  • Redesign of housekeeping and archiving concepts  

Conclusion
HANA Migration is not a change of the database, but rather it needs to be planned with an appropriate lead time. All processes have to be tested for optimization potentials to get the maximum benefit from SAP HANA.

Get in touch with us

Are you also facing a migration to SAP HANA and interested in an exchange of experience? Please don’t hesitate to contact us and we will arrange a workshop on „HANA Migration Best Practices“. During the workshop you will learn about technical details, which have to be considered in the scope of the migration, and we will also provide you with recommendations for a successful procedure model.

Contact:                     
Waldemar Fix