Native HANA project approach to migrate HANA 1.0 to HANA 2.0

In this blog, I am going to highlight on the approaches which will give a detail view of which option we will implement for migration of HANA DB 1.0 SPS12 version to HANA 2.0 SPS 04 or 05 in a ongoing Native HANA Project.

In one approach only DB upgrade is required and no application server upgrade is required and only limited to the basis team activity. In the other approaches along with HANA DB upgrade Application Server(XS server ) need to the upgraded and developer involved in lots of activities.

Let’s discuss about the approaches which we can follow for migration –

## Hybrid Approach :

If we go though the details HANA platform Architecture in Native HANA view it looks like below –

In Hybrid Approach HANA DB artifacts exposed to outside client through XS classic in this architecture via OData  and XSJS in HANA 1.0 SP 12.

Now in this Hybrid approach after upgrading to HANA 2.0 SPS 04 or 05, app server XS classic and XS advance but we will keep the XS classic also. We will keep the existing land scape where the DB artifacts and content object can be accessed via HANA Studio and the existing report and development works do not have any impact.

In this approach we will upgrade HANA DB to 2.0 and slowly migrate to XSA and slowly will change the XS Classic object XS Advanced object migration. I this migration we will use HANA Web IDE for development and GitHub as a repository control with version management. The approach should look like below –

## HANA DB upgrade and XSA Migration Sametime:

In this approach at the same time we will upgrade the HANA DB to 2.0 SPS 04 or 05 Version and Migrate to XS advanced environment one by one. XSA include Multi-Tenant Container approach in the database which is more complicated and required a signification amount from developer team to migrate the existing environment and object to XSA environment. This approach is very risky also in terms of project deliverables .The approach should look like same as above but different is all about the migration timing which look like below –

## Upgrade HANA DB 2.0 Only:

In this approach we will upgrade the HANA DB to 2.0 SPS 04 or 05 Version only. Developer and modeler will continue using XS classic with HANA studio tool for model and development.

Using HANA Studio we can utilize some function of HANA 2.0 but not full feature. In this approach we will require less effort and smoke test is ok for confirmation about the upgradation success.

The approach should look like the below diagram –

As per my suggestion Hybrid Approach is the best way for HANA DB upgradation from Native HANA project perspective. I was involved in two project and we use this approach which was very successful.