On 07/05/2013 02:12 AM, Arulappan, Arul Shaji wrote:
> - Support for UTF16 column encoding and representing NCHAR and
> NVARCHAR columns in UTF16 encoding in all databases.
>> Why do yo need UTF-16 as the database encoding? UTF-8 is already
> supported,
>> and any UTF-16 character can be represented in UTF-8 as far as I know.
>>
> Yes, that's correct. However there are advantages in using UTF-16
> encoding for those characters that are always going to take atleast
> two-bytes to represent.
>
Any suggestion to store data in utf-16 is likely to be a complete
non-starter. I suggest you research our previously stated requirements
for server side encodings.
cheers
andrew
