While planning our storage needs for the next two years I wonder what the plans presented at the MaxDB Info day (I think in 2007) to use CESU-8 for database storage are doing.
Even if we load a database with UseUnicodeColumnCompression = YES the saved space is less than 10 % although the majority of the data in the system is ASCII (Latin-1).
We grow roughly 2 - 4 GB/day and are already at 2,7 TB. If that database is migrated to Oracle as it is, we need less than half of the storage.
What are the plans to change from UTF-16 and if they are still valid, what version will support that and how much time do we need to estimate until it's available?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.