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...

  • I have to admint I did not spent too much time reading all the posts carefully but I think I did not find anyone suggesting the usage of the sysmessages table. We create software for the international markets and we have to support a whole set of languages. All our translations are stored in sysmessages tables. The nice thing about this apoproach is that you can use bulid in SQL function FORMATMESSAGE to deliver the translated text to you. On top of this the mesasges could be parametrized so you do not have to worry about the proper string concatenation to create a proper message in a given order (Many languages have different sentence structure).

    In your tables you just have to store the ID of the message stored in sysmessages (and any replacement parameters if you use them) and depending on the connection string options your application is displaying everything in the correct language.

    ---------------------------------------------
    [font="Verdana"]Nothing is impossible.
    It is just a matter of time and money.[/font]