Skip to Content
avatar image
Former Member

SAP HANA NLS

Can you please provide me the below information based on your past experience on other clients: •        Should NLS implementation be performed before or after HANA migration activities? What are the pros and cons? •        Oracle is Row based technology and HANA and Sybase are Column based technology. Can NLS be connected to migrated HANA environments afterwards? •        Can we integrate another Sybase database with Sybase IQ NLS database after NLS implementation and what are the pros and cons? It will be appreciated if you please send me the above information asap. Thanks in Advance

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 05, 2015 at 03:08 PM

    Hi Siva,

    I would says it depends on your current DB size and the migration procedure.

    However, you should be aware one important fact, which SAP did not tell us end of 2013, when they wrote a NLS concept for us...

    Just yesterday my frustration exploded here: http://scn.sap.com/message/16337625

    From my point of view NLS is not developed sophisticatedly!

    You have to be aware of many topics which could lead to issues in your daily application management...

    Three problematic examples - besides the issue in my posting above:

    1) If you extract ERP data and for what ever reason the datasource delivers records with a date, which has already been used for archiving, then your DSO activation will fail and you have to reload all data back until that date for being able to activate

    (Only alternative is, you implement a deletion routine, but then of course this data is not updated in the DSO)

    2) If you should load data records (e.g. coming from external source) where the key fields like document number and item are repeated (number range started all over again), you could have the old data archived and the same numbers again in active DSO table. Now want to reload from NLS for reason in 1) --> Forget about it! Re-Loading fails due to "duplicate key" and there is no proper (standard solution) to e.g. chose skip or overwrite DSO data. This is embarrasing!

    3) If you have archived your write-optimized DSOs, just in case for being able to delete the upper Layers and reload everything with new TRFN logic, for example ... you would assume you can just trigger a DTP which also reads the archive. --> Forget about it! First, you have to re-load ALL records from the archive, otherwise the upload to the next layer will not be in correct sort order! The w/o-DSO is capable to load request-based in the DTP, NLS is not.

    These are only the "highlights", which you should consider in your Appl. Mgmt.

    Best regards,

    Martin

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Manpreet Singh

      Hi All,

      Issue while archiving data using NLS from wdso(Write Optimized Data Store Object) is "Data area archived Empty".

      Please go through the following link

  • Nov 02, 2015 at 11:06 AM

    Hi Siva,

    Below docs might be helpful to you.

    SAP First Guidance - SAP-NLS Solution with SAP IQ

    Also have a look at the docs submitted by @Roland Kramer

    Regards,

    Vengal.

    Add comment
    10|10000 characters needed characters exceeded