Skip to Content
-1

Hana db sizing from non-unicode system

What is the difference in target hana db size when migration / conversion done from source system being unicode and non-unicode.

Generally for non-hana migration, source and target same databases, the db size increase after migration to unicode. So the above query.

Regards, Subhash

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 26 at 09:27 AM

    Hello Subhash,

    There are 3 sizing factors to consider when migrating from a non Unicode database onto SAP HANA:

    • Unicode needs more space since one character is potentially coded as more than one byte.
    • The export and subsequent import reorganises the database which if not done lately can decrease the space it occupies considerably.
    • SAP HANA uses columnar storage for some table that can result in considerable compression.

    I would therefore suggest that you run a Suite on HANA memory Sizing report.

    Best regards

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks,

      This report was executed in the system. It shows more GB allotted to rows than column structure.

      The db size earlier is 6TB, the column figure shows 200GB and rows figure shows 2.5TB.

      This was the main reason behind my question. Why the rows size is so high after the report. Was it because of system is non unicode?