Switching over to new HANA hardware

Basically the migration to the new HANA server is done via a backup/restore.
Difficult part was that this HANA server got its data from SAP ECC via a SAP SLT server.
So replication and database triggers should be taken into account when switching over.

The connections between the applications look like:

Adjust SLT connection to HANA MCD

After convert HANA to MCD (MultiTenant) some tasks must to be executed in SLT to connect with MCD Database.

In addition to Note 2101084 please check the SAP Note relevant for your DMIS version from the list below and ensure all corrections are applied to both source and SLT server where indicated in the note.

• 2016511 - Installation/Upgrade SLT - DMIS 2011 SP7
• 1958809 - Installation/Upgrade SLT - DMIS 2011 SP6 / DMIS 2010 SP10
• 1882433 - Installation/Upgrade SLT - DMIS 2011 SP5
• 1824710 - Installation/Upgrade SLT - DMIS 2011 SP4 / 2010 SP9
• 1759156 - Installation/Upgrade SLT - DMIS 2011 SP3 / 2010 SP8
• 1709225 - Installation/Upgrade SLT - DMIS 2010 SP7 / 2011 SP2
• 2191214 - Installation/Upgrade SLT - DMIS 2011 SP9 & SP10 

HANA Live implementation (sidecar scenario)

In this “how-to” post I am aiming to cover additional parts that arise while using HANA Live models in a sidecar scenario to your main (mature) SAP installation on a different DB. This blog post is of lesser interest for those cases, where an existing ECC / CRM system is migrated to HANA DB due to the fact that required tables are readily available under SAP_ECC / SAP_CRM schema. All you need to do is – install the HANA Live content and start using / modifying it.

Just a short recap, the scenario I am trying to cover here is the least-risk (and, possibly, cost) approach to leverage advantages of HANA with minor changes to existing ECC/CRM landscape, when an additional HANA instance is connected to the “main” system, running on traditional relational database. It may be an own HANA box, or any of the cloud solutions on the market.