Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234

Multiple Language Database Design - Additional Columns vs. Additional Tables... Expand / Collapse
Author
Message
Posted Sunday, June 14, 2009 8:11 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, July 27, 2014 12:14 PM
Points: 3,433, Visits: 14,423
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
Post #734759
Posted Monday, June 15, 2009 3:26 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, February 2, 2013 8:21 AM
Points: 283, Visits: 268
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 .


Post #734848
Posted Monday, June 15, 2009 10:15 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, October 11, 2009 3:17 PM
Points: 23, 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?

Post #735428
Posted Tuesday, June 16, 2009 6:12 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, February 2, 2013 8:21 AM
Points: 283, Visits: 268
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.


Post #735577
Posted Tuesday, June 16, 2009 6:31 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, July 27, 2014 12:14 PM
Points: 3,433, Visits: 14,423
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
Post #735591
Posted Wednesday, August 19, 2009 7:20 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, July 27, 2014 12:14 PM
Points: 3,433, Visits: 14,423
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







Kind regards,
Gift Peddie
Post #773976
Posted Thursday, August 20, 2009 7:47 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, March 29, 2011 2:59 PM
Points: 473, 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.
Post #774206
Posted Friday, August 21, 2009 2:01 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, July 27, 2014 12:14 PM
Points: 3,433, Visits: 14,423
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
Post #775411
Posted Tuesday, September 1, 2009 2:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, September 1, 2009 2:29 AM
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
Post #780502
Posted Thursday, October 7, 2010 5:30 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, September 4, 2012 2:14 AM
Points: 14, Visits: 93
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>

Post #1000310
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse