Earlier this year, in September 2020, we had outlined our plans and the rationale behind introducing SAP HANA version 2.0 in the SAP Cloud Platform, Neo environment. The new HANA version 2.0, was intended to provide a path forward for HANA database systems with version 1.0 – which will reach End-of-Maintenance on June 30th, 2021; and also provide a logical milestone for HANA customers on Neo to eventually migrate to the target state with SAP HANA Cloud.
HANA 2.0 is here!!
As a first milestone release towards this goal, we are pleased to announce the availability of SAP HANA version 2.0 on the Neo environment.
Note that this version will currently be available only for ‘new’ database provisionings; meaning, in case you have free quota of SAP HANA entitlements in your Neo environment subaccounts, you will now be able to provision new SAP HANA 2.0 systems.
But what about existing HANA 1.0 systems?
Currently upgrading HANA 1.0 database systems to version 2.0 is not supported yet. The version upgrade functionality is planned to be released in the next milestone i.e. early 2021. Once this feature is available you will be able to upgrade existing HANA 1.0 systems to 2.0.
I already have running HANA 1.0 database systems. What should I do?
Actions required from you depends on your current HANA system configuration.
Are you running a HANA 1.0 Tenant database ‘MDC’ system?
If yes, you are good for now. After the next milestone release, you will be able to upgrade your existing HANA system from version 1.0 to 2.0. This upgrade should be as simple as any other HANA version upgrade you have carried out until now.
Meanwhile, you should read through the materials on HANA 2.0 in Neo, to get yourself acquainted with supported/unsupported features, restrictions and feel free to reach out in case of questions.
Are you running a HANA 1.0 single-container ‘XS’ system?
In this first milestone, we have also additionally released the HANA ‘XS’ to ‘MDC’ conversion feature as a Cloud cockpit self-service, in BETA availability.
This feature can be used to convert existing HANA XS systems to HANA MDC systems. This conversion is essential because HANA being configured in the ‘Multitenant Database Container’ or ‘MDC’ configuration is a prerequisite for the possibility of upgrading existing HANA 1.0 systems to version 2.0.
The conversion self-service has been constructed to check your HANA system for the fulfillment of the necessary pre-requisites in order for the conversion to succeed.
The checks will report Errors (to be fixed) and Warnings (to be accepted) that need to be addressed before moving forward with a version upgrade. A list of pre-requisite checks and corresponding recommended solutions have been detailed here.
Once the check goes through, the conversion of your XS system to an MDC can start. It is important to note that the conversion does involve a downtime but does not require any rebind.
As the conversion feature is only made available as a BETA functionality, you will be able to try out the feature on ‘BETA’-enabled subaccounts. And as with all BETA features, the conversion should currently be used to run tests and validations on your development or quality systems only.
It is highly recommended to wait for the General Availability (GA) of the conversion feature before applying it to your production systems/landscapes.
Post the GA release of the conversion feature and release of the HANA 2.0 version upgrade feature, in the next milestone, you will be able to apply your learnings and convert your production HANA database systems to MDC and upgrade them to HANA 2.0.
Try out the XS to MDC conversion self-service on your Dev/QA systems to understand how it works and to foresee potential issues.
Follow this blog for updates on the release of the next milestone in early 2021.
In case you have further queries on this topic, please write to email@example.com with ‘HANA 2.0 on Neo’ in the email subject for prompt responses.