web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / NAV 2013 Localization
Microsoft Dynamics NAV (Archived)

NAV 2013 Localization

(0) ShareShare
ReportReport
Posted on by Community Member

Hello Team,

We currently have GB localization with us....If we want to have different localization also, do we need to have different database for different localization or single database can handle various localization? And how to implement various localization.

Also what is the best way for handling localization means either through SQL instance or NAV instance etc.

Please advise.

Best Regrds

Rishi Raj

*This post is locked for comments

I have the same question (0)
  • Verified answer
    jcastro Profile Picture
    jcastro 2,245 on at

    Hello Rishi,

    I am not quite sure it's the best idea to try to handle different localizations with a single database. From my experience, it's much easier to have one per each. You will never have to fear some update affecting a common object in a way that can't be adapted for both localizations (different updates per country).

    Also, I'd say that the end customer's license cannot have both country codes in it. It is my believe it is "single localization" only. So you'd need two licenses either way.

    Why do you need to do it in a single database?

    As far as handling in SQL instances, you can perfectly run two localized versions different between them in the same SQL instance. The problem you might run into is when trying to run the NAV Server. Differences in builds (which is a probably thing to ocurr) makes the NAV server do some weird things. I've lived that and it's frustrating. Best approach from my perspective would be different NAV servers on different machines (although not necessarily different SQL Servers) if possible, unless it's a testing environment you don't plan on updating.

  • Community Member Profile Picture
    Community Member on at

    Hello Jose,

    Thanks for your reply,

    BR

    Rishi

  • Community Member Profile Picture
    Community Member on at

    Hello Jose,

    Just need to update myself with some more clarification as if we need to implement different localization, we need to have two different databases( SQL server can be same),different NAV server installed on different machines  & different license for each localization.

    Please correct me if misunderstood some statement.

    Thanks

    Rishi Raj

  • Suggested answer
    jcastro Profile Picture
    jcastro 2,245 on at

    You are absolutely correct. That is what (from my perspective) will be easier to manage afterwards.

    Although if you feel that two machines, one for each NAV server for each localization is a little too much, you can check out this link which explains how to set up different NAV servers on the same machine with dfifferent builds each. You just need to be careful afterwards.

    community.dynamics.com/.../126789.aspx

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans