June 10, 2005 at 4:56 am
|
June 10, 2005 at 7:03 am
- you could go for N(var)char solutions and avoid collation issues.
- if you're using a database per collation, _all_ interdb stuff has to perform collation translation to be compatible. Check out http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=4&messageid=95954
- if you're choosing for a collation per column, offcourse if you want to compare colx to coly you'll need to perform collationtranslation.
If you only want e.g. have some translation tables like
create table mytranslations (
code1 char(4)
, UsEnglishtext varchar(256) COLLATE SQL_Latin1_General_CP1_CS_AS
, Germantext varchar(256) COLLATE German_PhoneBook_CI_AI
, ChineesText varchar(256) COLLATE Chinese_Taiwan_Stroke_CI_AI)
code1 UsEnglishtext, Germantext, Chineesetext
aaa mytext meintekst "number43"
There may be no problem if your queries don't mix collations.
I hope this gets you on track ...
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
June 13, 2005 at 2:42 am
Ok! I'll try to use unicode strings... 🙂
thank you very much!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply