UseUnicodeColumnCompression - Migration Scenario

[jenswieduwilt]

Dear all,

we did a migration from Oracle to MaxDB, combined with a unicode conversion. Now of course our database size increased.

I know that MaxDB doesn't support UTF-8 at moment, but now I found an interesting parameter für compression of the non-key fields in tables.

I hope, that I can reduce the databse size with this parameter.

The parameter is: UseUnicodeColumnCompression

Do you have experience with this parameter?

Did you have problems after activating the parameter?

The problem is, that the parameter works only for new created tables.

In SAP note 1006496 you can find a statement, that can be used to alter existing tables:

ALTER TABLE ... PACKED UNICODE

Did anybody of you write a script to convert all the existing tables in your SAP-System to compressed tables? It would be nice, if you could share this script.

Or is there any other migration scenario like export/import?

Best regards,

Jens

[markus_doehr2]

we did a migration from Oracle to MaxDB, combined with a unicode conversion. Now of course our database size increased.

I know that MaxDB doesn't support UTF-8 at moment, but now I found an interesting parameter für compression of the non-key fields in tables.

I hope, that I can reduce the databse size with this parameter.

Out of my experiences and our test runs the 'compression factor' is less that 2 % - so almost non-existing.

Markus