Skip to Content

Transportation best practices in Native SAP HANA

Hi Team,

Here is my scenario.

We have native SAP HANA (SPS12) system used for mainly Analytics, no web-development at this point.

We have data coming in from different data sources either loading into HANA or through virtual tables. Following are the most frequently created objects in HANA by our team.

1) Custom Schemas

2) Virtual Tables using SDI Adapters

3) Physical Tables

4) Procedures

5) Table Functions

6) Calculation Views

7) Analytic Privileges

8) Roles

9) Users

Ideally we want to handle transportation of these objects via HANA LM using DU & Change Recording.

I know that we can handle objects 1,3,4,6,7,8 transportation by creating them as repository objects (creating objects in development perspective).

I am looking for your advises on 2,5,9 object types transportation. HDI containes in SPS12 XSA seems like an option, however system generated schema names looks awkward for Analytical System.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    May 15, 2017 at 12:51 PM

    Table functions (HDBSCALARFUNCTION and HDBTABLEFUNCTION) can be repository objects and transported as well.

    HDI is definitely the long term replacement however. It does handle more objects than the old repository + DUs. You can override the generated schema names and supply your own Schema name as well.

    Add comment
    10|10000 characters needed characters exceeded