SQL Server 2005 CodePage Issue?

Edit: A CLR function might be your only bet to use Remus' suggestion of MultiByteToWideChar.

Yes, two varchar characters to store 1 unicode character. – John Ptacek Jan 5 '10 at 21:02 1 cast I don't think it will work. It will cast each individual byte in the multibyte set to its unicode equivalent.

The correct translation is by going through MultiByteToWideChar msdn.microsoft. Com/en-us/library/cc500362. Aspx and I don't think this functionality is available as T-SQL – Remus Rusanu Jan 5 '10 at 21:16 @Remus: it was a long shot anyway,,, – gbn Jan 5 '10 at 21:43 I have previously looked at the COLLATE clause using the various Simplified Chinese for the codepage we are using (936).

These did not resolve the issue either. I am not well-versed in COLLATE, but is it more geared towards how the sorting happens than translating? It DID however result in a different value for the string – John Ptacek Jan 5 '10 at 23:20 @jptacek: and comparison.It was a guess.

– gbn Jan 5 '107 at 5:57.

What we ended up doing for this is writing a CLR function that can be called from our SQL statement. We pass in the string and the desired code page and get a converted string returned. The performance is not what we hoped for, but it seemed to be the only path we could find.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.