A database is currently configured with the database character set to WEBIS08859P1 and national character set to AL16UTF16.

Business requirements dictate the need to expand language requirements beyond the current character set, for Asian and additional Western European languages, in the form of customer names and addresses.

Which solution saves space storing Asian characters and maintains consistent character manipulation performance?

For storing Asian languages efficiently, AL16UTF16 (fixed 2-byte per character) is optimal because it uses consistent space regardless of the character, unlike UTF8 which uses 1-3 bytes variably. NCHAR data types with AL16UTF16 national character set saves space for Asian characters while maintaining consistent character manipulation performance. Changing to UTF8 would increase storage requirements for Asian characters (3 bytes each instead of 2).