mibuso.com
Home› SQL General
Options

Servers for SQL databases - HU, PL, CZ, RO cases

clairvoyantclairvoyant Member Posts: 11
edited 2010-08-27 in SQL General
Hi,

We are planning install NAV databases for HU, PL, CZ and RO. Since their languages belong to Latin2 family, I decided to install them on a separate SQL Server whose non-Unicode support is set to one of the languages of these countries.

Is there anyone who has experienced NAV database installation for these countries ? I'm wondering if we can place them in Latin1 server whose non-Unicode support is set English (United States) or not.

Thanks.

Comments

  • Options
    clairvoyantclairvoyant Member Posts: 11
    I need to learn how to use forum :)

    An admin can move this topic under Other-> SQL General ?

    Thanks.
  • Options
    krikikriki Member, Moderator Posts: 9,090
    Don't worry, you'll learn. You can't be a specialist starting with your first post. :-)

    PS: instead of writing a new post to ask to move the topic, you can use the reporting function (the red '!' at the right of the post) and report as "wrong forum".

    [Topic moved from 'NAV/Navision Classic Client' forum to 'SQL General' forum]
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • Options
    kinekine Member Posts: 12,562
    clairvoyant wrote:
    Hi,

    We are planning install NAV databases for HU, PL, CZ and RO. Since their languages belong to Latin2 family, I decided to install them on a separate SQL Server whose non-Unicode support is set to one of the languages of these countries.

    Is there anyone who has experienced NAV database installation for these countries ? I'm wondering if we can place them in Latin1 server whose non-Unicode support is set English (United States) or not.

    Thanks.

    The language for non-unicode apps doesn't matter on the SQL server. You need correct collation on the SQL. You need to have the language for non-unicode apps correctly set on machine, where the NAV client or NAS will be running. If you need assistance for implementing CZ db, do not hesitate and contact me, we can arrange support for you in any area...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    clairvoyantclairvoyant Member Posts: 11
    Hi kine,

    Are you sure about that non-Unicode option should be changed on the server where NAV client install, not on SQL Server ?

    If yes, what should be the collation of database, Latin1_General or a proper collation according to language that we want to use ?

    Thanks.
  • Options
    kinekine Member Posts: 12,562
    Of course, best is to have the collation same as the used language. If you want to have all companies in one DB, than you can use the Latin2 collation, if you will have separate DB for each company, you can have e.g. Czech collation for Czech DB (there is one specific problem with Czech sorting with character 'ch' which is one character in Czech alphabet, which could be solved by using collation 81 or 82 if I remember correctly - it is Latin 2 characters with Latin 1 sorting, but it is not correct sorting for Czech alphabet).
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    clairvoyantclairvoyant Member Posts: 11
    We are planning to create a separate database for each company. We have a discussion regarding non-Unicode set up for OS. And seems this options should be set in NAV client machine, not SQL. In one aspect, that's a good news we don't need to touch what we have now in SQL side.

    So, for collation, You are right about the sorting problems. Probably, best option is where the system do sort the best :)

    Thank you very much for the info !
Sign In or Register to comment.