Home Forums SQL Server 7,2000 Globalization Multiple Language Database Design - Additional Columns vs. Additional Tables... RE: Multiple Language Database Design - Additional Columns vs. Additional Tables...

  • 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?