All your database code is neat and tidy. You’re prepared to migrate to SAP HANA, which promises blistering processing speeds. So just plug that code into the new environment and you’re ready to fly like a fighter pilot, right?
Umm, not quite.
When you migrate to SAP HANA, nearly all standard code on your existing platform will run the same way on SAP HANA. And most of your custom code will also work as you’d expect.
But some underlying database characteristics change when you move to HANA, so there may be a few parts of your custom code you’ll have to deal with. Here’s a quick look:
- You’ll need to replace code that relies on database-specific features, such as native SQL. Instead, you need a database-independent statement set called Open SQL, which will run on any database.
- SAP HANA switches your data from a row-based to a column-based architecture, so you will need to replace code that relies on implicit sorting.
- The migration to a column-based database also converts pool and cluster tables into transparent tables.
Actually, rewriting your custom code isn’t the hard part: Finding the code that needs changing is what strains tempers. Fortunately, there are SAP tools available for customers migrating to HANA – for example, the ABAP Code Inspector, which is essential for defining variants of elements you want to analyze.
This short outline identified some basic problems that crop up with data switchover of custom code. But how do you identify which parts of your code most need to be optimized to work with SAP HANA?
Oh, wouldn’t you like to know! Click here next time to find out.
— written by Simen Huuse, Consultant, itelligence AS —