HANA News Blog
DMOVE2S4 and Homogeneous option for SUM DMO
Jens Gleichmann • 25. Oktober 2023
Spotlight on for Homogeneous option for DMO and DMOVE2S4 aka “DMO move to SAP S/4HANA (on hyperscaler)”
Homogeneous option for DMO (with system move)
DMO used to be heterogeneous (change of DB). Now you can use DMO with system move (also on-prem to target on-prem) to migrate and convert ECC on HANA to S/4 or just update/upgrade S/4 and move it to another location like other DC or other instance in one step.
- SAP BW or SAP BW/4HANA systems are not supported
- target “SAP ERP on SAP HANA” is not supported
- only *HANA to S/4: Only target product SAP S/4HANA is supported
- can also be used on prem (e.g. ERP 6.0 on HANA to S/4)
- doDMO and doC are supported for homogeneous DMO since SUM 2.0 SP18
- no rename of SID in the procedure possible (separate step afterwards needed)
- possibility to retain the source after SUM procedure
- R3load file mode is used
DMOVE2S4 aka “DMO move to SAP S/4HANA (on hyperscaler)”
The DMOVE2S4 is just to move and convert to the "cloud" in one step. This includes also anyDB source systems and downtime-optimization techniques (doDMO and doC). SAP illustrates it as cloud but, you can also use another DC or another hoster.
- Approach is not a SUM option => more a combination of SUM features and options
- alternative to “DMO with system move”
- plain-DMO
- Only target product SAP S/4HANA is supported
- Approach works for source systems on anyDB as well as on SAP HANA DB
- R3load pipe mode is used, not file mode
- prerequiste: Latency < 20 ms between source and target
- prerequiste: Bandwidth > 400 MBit/s
- SUM runs a latency check
- doDMO and doC are supported for homogeneous DMO since SUM 2.0 SP18
- no rename of SID in the procedure possible (separate step afterwards needed)
- no official possibility to retain the source after SUM procedure
- ASCS which is not running with a AAS (=standalone) cannot be moved as standalone within the procedure => it will run within one AAS
=> Due to the fact that the R3load pipeline mode is used this option is faster compared to the "normal" DMO system move approach.
SAP HANA News by XLC
In the world of modern database management systems, query performance is not just a matter of hardware—it’s about smart execution plans. At the core of generating these plans lies a critical component: optimizer statistics.
This article explores why databases need optimizer statistics, with particular emphasis on SAP HANA, while drawing parallels with Oracle, Microsoft SQL Server (MSSQL), and IBM DB2.
Please notice that when you want to run HANA 2.0 SPS07, you need defined OS levels. As you can see RHEL7 and SLES12 are not certified for SPS07. The SPS07 release of HANA is the basis for the S/4HANA release 2023 which is my recommended go-to release for the next years. Keep in mind that you have to go to SPS07 when you are running SPS06 because it will run out of maintenance end of 2023.
With SPS06 and even stronger in SPS07 the HEX engine was pushed to be used more often. This results on the one hand side in easy scenario to perfect results with lower memory and CPU consumption ending up in faster response times. But in scenarios with FAE (for all entries) together with FDA (fast data access), it can result in bad performance. After some customers upgraded their first systems to SPS07 I recommended to wait for Rev. 73/74. But some started early with Rev. 71/72 and we had to troubleshoot many statement. If you have similar performance issues after the upgrade to SPS07 feel free to contact us! Our current recommendation is to use Rev. 74 with some workarounds. The performance degradation is extreme in systems like EWM and BW with high analytical workload.
A database optimizer behaves similarly to the navigation system in your car. You use various parameters to determine which route you want to take to reach a particular destination. Potential additional costs for tolls and ferries also play a role, as do other limitations such as the vehicle's height, length, and width. From these input parameters, the navigation system determines the optimal route based on current traffic information (traffic volume, construction sites, congestion, accidents, closures, etc.), weather conditions, and the length of the route. This means that with exactly identical input parameters, different routes, costs, and thus different travel times can arise depending on the given conditions.
Most of our presentations on data tiering projects end with these typical questions:
How much we will save?
How fast can it be implemented?
Is the effort worth it over time?
My counter question:
"Do you know how much 1 GB of memory costs your company per month or year?"
=> how much memory we have to save to be beneficial?
Unser erster Buch mit dem Titel "SAP HANA Deepdive: Optimierung und Stabilität im Betrieb" ist erschienen.
Recently handelsblatt released an article with a new SAP RISE option called SAP ERP, private edition, transition option. This option includes a extended maintenance until the end 2033. This means 3 years more compared to the original on-prem extended maintenance. This statement was confirmed by SAP on request of handelsblatt, but customers receive more details, such as the price, in the first half of the year. This is a quite unusual move of SAP without any official statement on the news page. Just to raise more doubts? Strategy? However a good move against the critics and the ever shorter timeline. Perhaps it is also a consequence of the growing shortage of experts for operating and migrating the large number of systems.
When it comes to optimizing SAP HANA, the balance between performance and cost efficiency is critical. I am happy to share a success story where we used the Native Storage Extension (NSE) to significantly optimize memory usage while being able to adjust the sizing at the end.
The Challenge: Our client was operating on a 4 TB memory SAP HANA system, where increasing data loads were driving up costs and memory usage. They needed a solution to right-size their system without compromising performance or scalability. The client wanted to use less hardware in the future.
The Solution: We implemented NSE to offload less frequently accessed data from memory. The activation was customized based on table usage patterns:
6 tables fully transitioned to NSE
1 table partially transitioned (single partition)
1 table transitioned by specific columns
SAP NSE was introduced with HANA 2.0 SPS04 and based on a similar approach like data aging. Data aging based on a application level approach which has a side effect if you are using a lot of Z-coding. You have to use special BADI's to access the correct data. This means you have to adapt your coding if you are using it for Z-tables or using not SAP standard functions for accessing the data in your Z-coding. In this blog we will talk about the technical aspects in more detail.
The SAP Enterprise Cloud Services Private Cloud Customer Center (PC3) - a new digital delivery engagement model dedicated to manage service delivery for RISE with SAP S/4HANA Cloud, private edition customers.