HANA News Blog

End of support in 2020 for HANA 2.0 SPS03

Jens Gleichmann • 6. Juni 2020

Bitte beachten Sie das Supportende von SPS03 im Juli 2020

SAP HANA 2.0

 

Im Juli 2020 endet der Support für HANA 2 SPS03 . Dies bedeutet, dass nach diesem Zeitpunkt keine neuen Maintenance Revisions mehr für SPS03 (aktuell letzte Revision 37.06) von SAP freigegeben werden. Daher sollten alle Kunden sofort auf die neueste HANA 2.0 SPS04 Revision upgraden.
SPS05 wird zwar ebenso in diesem Zeitraum freigegeben, sollte aber erst nach etwas
"Reifezeit" konsumiert werden. Dieses Release wird anders als bisherige nicht 2 Jahre Support, sondern 5 Jahre "long Term" Support erhalten. SPS06 wird dann wieder voraussichtlich 2 Jahre Support erhalten.
Jeder Upgrade birgt Gefahren hinsichtlich Stabilität und Performance, daher sollte dies mit der nötigen Sorgfalt getestet werden. Wir
unterstützen Sie gerne mit unserer Erfahrung bei Upgrades oder anstehenden Herausforderungen hinsichtlich Performance oder Stabilität.


Support for
HANA 2 SPS03 will end in July 2020 . This means that after this point in time, no new maintenance revisions for SPS03 (currently last revision 37.06) will be released by SAP. Therefore, all customers should immediately upgrade to the latest HANA 2.0 SPS04 revision.
SPS05 will also be released during this period, but should only be consumed after a bit of
"maturing time" . Unlike previous releases, this release will not receive 2 years of support, but 5 years of "long term" support . SPS06 will then probably receive 2 years of support again.
Every upgrade is dangerous in terms of stability and performance, so this should be tested with the necessary care. We would be happy to support you with our experience with upgrades or upcoming challenges in terms of performance or stability.

 
Details:

 

2378962 - SAP HANA 2.0 Revision and Maintenance Strategy

 

SAP HANA 2.0 Revision Strategy


End of Support HANA 2.0 SPS06

 

SAP HANA News by XLC

More time to switch from BSoH to S/4HANA
von Jens Gleichmann 21. Januar 2025
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.
Optimize your SAP HANA with NSE
von Matthias Sander 15. Januar 2025
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 HANA NSE - a technical deepdive with Q&A
von Jens Gleichmann 6. Januar 2025
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
von Jens Gleichmann 5. Januar 2025
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.
Proactive maintenance for SAP RISE will start now in 2025
von Jens Gleichmann 5. Januar 2025
Proactive maintenance for SAP RISE will start now in 2025 with minor tasks like updating SPAM/SAINT and ST-PI / ST-A/PI. For those companies which are familiar with frequent maintenance windows, they are good to have such time frames to hold the systems up-to-date and secure. However, for larger companies where such frequent maintenance windows are not common because every minute of downtime is costly and may only really be necessary once, the situation is quite different.
Dynamic Aging for NSE - combined with Threshold and Interval option
von Jens Gleichmann 28. Dezember 2024
Dynamic Aging makes it possible to automatically manage at which point in time older partitions can be moved to the 'warm' data store. The data in a new OTHERS partition is 'hot' data, that is, stored in memory with the load-unit attribute implicitly set to COLUMN LOADABLE. As an extension of the Dynamic Range Partitioning feature Dynamic Aging makes it possible to automatically manage when older partitions can be moved to the 'warm' data store (Native Storage Extension) with the load-unit attribute for the partition set to PAGE LOADABLE. Warm data is then stored on disk and only loaded to memory when required. Dynamic Aging can be used with both THRESHOLD mode (defining a maximum row count number in partition OTHERS) and INTERVAL mode (defining a maximum time or other numeric interval between each new partition). For example, for a partitioned table which is managed by dynamic partitioning and containing date/time information, you can specify an age limit (for example six months) so that when data in an ol
automatic maintenance of the 'others' partition
von Jens Gleichmann 28. Dezember 2024
You can create partitions with a dynamic others partition by including the DYNAMIC keyword in the command when you create the partition, this can be used with either a THRESHOLD value to define a maximum row count number or an INTERVAL value which can be used to define a maximum time or other numeric 'distance' value. The partition can be either a single level or a second level RANGE partition and dynamic ranges can be used with both balanced and heterogeneous partitioning scenarios.
HANA Range Partitioning details
von Jens Gleichmann 23. Dezember 2024
For heterogeneous partitioning schemas Dynamic Range Partitioning is available to support the automatic maintenance of the 'others' partition. When you create an OTHERS partition there is a risk that over time it could overflow and require further maintenance. Using the dynamic range feature the others partition is monitored by a background job and will be automatically split into an additional range partition when it reaches a predefined size threshold. The background job also checks for empty partitions and if a range partition is found to be empty it is automatically merged to neighboring empty partitions (the others partition is never automatically deleted).
A success story regarding BW/4HANA and different data tiering and optimization methodes.
von Jens Gleichmann 20. Dezember 2024
A success story regarding BW/4HANA and different data tiering and optimization methodes. 1) Removed overhead in key attributes which reduced the PK size (often more than 50% of the overall table size) 2) optimized the partitioning design 3) used NSE for write optimized ADSOs 4) introduced NSE for several ADSOs 5) optimized usage of inverted individual indexes
ACDOCA table growth - how to handle it
von Jens Gleichmann 10. Dezember 2024
ACDOCA table growth - how to handle it in a S/4HANA system
more
Share by: