Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Multiple Language Database Design - Additional Columns vs. Additional Tables...


Multiple Language Database Design - Additional Columns vs. Additional Tables...

Author
Message
Gift Peddie
Gift Peddie
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3474 Visits: 14456
This thread is actually about doing that only you need three columns because Arabic is right to left language, Korean does not use the Latin alphabet it comes with the more than 2000 character east Asian languages alphabet and English uses the Latin alphabets. The reason we are counting bytes and all three falls under three separate bytes ranges.

Kind regards,
Gift Peddie
tymberwyld
tymberwyld
SSC Veteran
SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)

Group: General Forum Members
Points: 286 Visits: 274
Most applications attempt to do this by having a single "NVARCHAR" column for FirstName, LastName, etc. This post is just about storing that information in a more efficient manner. You could probably attempt the single NVARHCAR column for you database at first. I think this post is starting to blend into content management for multi-lingural sites as well ;-).



Adrian Robertson
Adrian Robertson
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 107
Thanks

I am able to store both Korean text and English in the same field (either for different records or for the same record) but the way I achieved this was by using the Korean_Wansung collation on the DB itself, rather than Latin_General

Just not sure whether this would then allow me to store other languages at the same time (such as Japanese or Thai), though I'm guessing not, especially when it comes to Thai as it's a more complex character set

So would it be fair to say that the collation can be set at a field level, rather than at a DB level?
tymberwyld
tymberwyld
SSC Veteran
SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)SSC Veteran (286 reputation)

Group: General Forum Members
Points: 286 Visits: 274
Yes. I'm not sure what the best approach is (hence why we have this thread going). You may be able to put your database back to "latin" and then add seperate columns for each language outside the "latin" scope. For example, you should be able to store English, Portuguese, Spanish (all latin languages) in one NVARCHAR column, then add others for Chinese, Korean, Japanese, etc. This thread was an attempt to make that all kind of transparent without having to add more columns and more complication over time as you want to support new languages.



Gift Peddie
Gift Peddie
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3474 Visits: 14456
This thread was an attempt to make that all kind of transparent without having to add more columns and more complication over time as you want to support new languages.


I am not sure I agree on the above point because yes Korean falls under the same alphabet scheme as Japanese but one version of Japanese is very hard to store so it depends and Thai is actually a right to left language like Arabic so it is not related to Korean.

Kind regards,
Gift Peddie
Gift Peddie
Gift Peddie
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3474 Visits: 14456
would not be so sure about that.

They issued a patent to Microsoft for the Cascading Style Sheets.


Microsoft is the victim of a frivolous data patent so I am hoping Redmond will help persuade the US Government from issuing patents that did not provide value but impede innovation.

http://news.yahoo.com/s/nf/20090819/bs_nf/68501

;-)

Hehe

Kind regards,
Gift Peddie
JacekO
JacekO
SSC-Addicted
SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)SSC-Addicted (489 reputation)

Group: General Forum Members
Points: 489 Visits: 606
Gift,

You just blew my mind off...

AMAZING.

It is not about the article (which is quite interesting in itself) but the fact you remembered about an obscure message posted several months ago related to this article...

I have hard time remembering what I had for breakfast yesterday...

---------------------------------------------
Nothing is impossible.
It is just a matter of time and money.

Gift Peddie
Gift Peddie
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3474 Visits: 14456
JacekO (8/20/2009)
Gift,

You just blew my mind off...

AMAZING.

It is not about the article (which is quite interesting in itself) but the fact you remembered about an obscure message posted several months ago related to this article...

I have hard time remembering what I had for breakfast yesterday...


Hi Jaceko,

Globalization posts are not obscure to me in most cases because I think you can develop in English add translated static content and use the same application in many languages as needed. If this thread is about Backup or other areas of SQL Server then it will be obscure to me.

Kind regards,
Gift Peddie
nasimhmd7
nasimhmd7
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 0
I think I was having problems with compatibility, so decided to unistall-reinstall, now, I can't get VS2008 to load an sdf file.
Natural Colon Cleanse
sam.walker
sam.walker
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 107
I might be shunned from the relational community, for making the mere point.

But if there is technology in place, which permits the storage/extraction of different language versions for a bit of text within a single field, and where we won't have to create these extra tables.

Is there any harm in encoding the data in to a single field, until such technology becomes available?

And could one way of doing this be with a tightly constrained XML field?

Sam


<Text>
<Translation locale="en-US" isDefault="True">G'day</Translation>
<Translation locale="en-GB">Good day to you</Translation>
<Translation locale="fr-FR">Bonjour</Translation>
</Text>


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search