Regarding 3 Tier Architecture of Nav 6.0

dillaa

I am working for a client where I am handling 14 countries databases seperately, as different countries has its own localized versions, so I want to understand that how 3 Tier of NAV 6.0 helps me in this type of scenario.

Marije_Brummel

No, this will not change a thing.

Try to focus on law regulations only. Most localised databases contain a lot of crap that has nothing to do with law or regulations.

p.willemse6

or keep it this way... the biggest NV sites worldwide are based on seperate databases...

Waldo

Indeed .. another (nasty) thing to keep in mind is the fact that it's only possible to add one country version in a license.

If you were able to merge all those localisation into one database, you should renumber all localisations to 50000-range to be able run them .

Seperate licenses, merge/renumber-jobs, ... often result in seperate databases.

p.willemse6

last thing you mention is allowed, when you pruchase a 1 user license for the foundation pack.

themave

Here is an interesting take on the one database

http://dynamicsuser.net/blogs/admin/archive/2007/10/25/why-will-microsoft-not-let-me-speak-about-dynamics-nav-at-convergence.aspx

Waldo

p.willemse6 wrote:

last thing you mention is allowed, when you pruchase a 1 user license for the foundation pack.

Yes, but it shouldn't have to be the case... .

David_Singleton

p.willemse6 wrote:

or keep it this way... the biggest NV sites worldwide are based on seperate databases...

I think you meant "some of ..." 8)

p.willemse6

yep.