CJ Butcher (cj@cjbutcher.com) writes:
Thanks for the attempted help Simon.
I've read the article before and am able to get UTF-8 characters into SQL,
the problem is getting them directly from Oracle, seems that DTS converts
the characters to UCS-2 during the transfer...and I don't want it to.
Storing Unicode data in SQL Server as UTF-8 is probably not a good idea.
There is no collation that understands UTF-8, so if you could get all
sorts of funny surprises when sorting or comparing UTF-8 data. You could
also get nasty surprises with conversion when retrieving or inserting
data, because the client will think that the data is something else
than what it is.
If you really insist of pushing down the squared peg through the round
hole, your best bet is probably to store the data as binary. Then at
least all bits would be in place, but there would still be a lot to lose.
The way to store Unicode data in SQL Server *is* UTF-16.
--
Erland Sommarskog, SQL Server MVP,
so****@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp