In our last entry, we looked at some of the problems that can crop up when migrating custom database code to SAP HANA. Basically, some of your code may run but be inefficient, so you don’t get the full “HANA effect” of revved up speed.
But not all this inefficient code is equally problematic. Some gets little use and so has little real effect. Then, how do you find which code most needs changing? Here’s an outline of the best – and quickest – approach to take.
SAP tools can lead you through a multi-level process that narrows your choices and pinpoints the areas that need special scrutiny.
First, the Code Inspector helps you locate all the code bits that could need changing.
But trying to correct every hit returned by the Code Inspector might be more exhausting than productive. To highlight code – both standard and custom – that gets the most intensive use, SAP provides the New SQL Monitor. You can activate it in your current SAP environment – even before migrating to HANA – without disturbing your processes. Its logs will identify which SQL statements are most expensive in runtime and load.
Finally, to pinpoint the real bad guys lurking within the list of code bits that the SQL Monitor log has identified as most data-intensive and time consuming, you can apply the SAP SQL Performance Tuning Worklist. This tool combines findings from both the Code Inspector and the SQL Monitor to point a finger at the exact bits of code where you can most productively place your effort – the ones with the greatest potential for optimization in HANA.
Now you’re clean and mean, ready for that blazing speed that only SAP HANA can bring.
– written by Simen Huuse, Consultant, itelligence AS –