Thank you for the option, but I want to stick with Microsoft technology.
Main Topics
Browse All TopicsHello, I have an SQL Server 2008 database using SQL_Latin1_General_CP1_CI_
Any advice would be appreciated.
Thanks~
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Well, unicode is multi-byte and needed for "special" characters. So you will want to change to a unicode basis. That also means making sure datatypes are unicode as well - e.g. instead of varchar, it then becomes nvarchar.
There is some reasonable documentation about "international considerations [SQL Server]" in books on-line and highly recommend you research that before you change anything.
Sorry, I haven't been getting any email notifications so I never bothered checking back. Thank you for the solution mark wills, that's good to know about the datatypes.
What I wound up doing was, in Management Studio, changing the collation on individual datatypes that could possible receive Japanese to the Japanese_Unicode collation (I was unaware this could be done). I noticed that text indeed becomes ntext, and varchar becomes nvarchar. Like you recommend.
I will probably just leave things as they are, because it's working fine...but are you in fact saying that I don't have to change the collation and just change the datatype?
Business Accounts
Answer for Membership
by: cs97jjm3Posted on 2008-10-16 at 13:25:43ID: 22735394
we had this a will ago and the then DBA used http://developer.mimer.com /collation s/index.tm l