Maintenance line needed for pure HANA DB migration project?

[Former Member]

Dear experts,

We are currently planning of a pure HANA DB migration project. The system landscape is a classical D-Q-P line. We are wondering if the ABAP transport has anything to do with the DB type. And any risk if we do not keep a separate maintenance line in the landscape? Do we have any SAP official statement or best practice for my question?

Thanks,

Alan

[Harald_Stevens · Accepted solution]

Dear Alan,

from a pure technical point of view transport between systems based on different DBs is possible. However, during a HANA migration project it is also strongly recommended to check your custom code for necessary (functional) and optional (performance) adjustments. Depending on the amount of changes you would like to perform prior to migration and the number of parallel projects it might be helpful to create a maintenance landscape.

Please note that most of the changes I am talking about (e.g. adding an 'order by' statement to a select on a cluster table) are also running on AnyDB and just ensure that the result set will be the same before and after the migration or that the performance will be the same or better on HANA. The only really DB specific statements are in the area of DB hints and exec SQL.

Additionally you should think about the length of the period where D and Q are already migrated and only P resides on the source DB. During that time you will have no possibility to test source DB specific issues (like consequences of adding an additional secondary index) before setting them live. If you can keep that period short, you might do without a maintenance landscape.

Kind regards

Harald

[Former Member · Accepted solution]

Dear Harald,

Thanks a lot for your answer.

Regards,

Alan