Cyrillic, Italian, English in 1 company on SQL with NAV 5.0

kriki

I searched for this but I didn't find anything conclusive.

We have 1 SQL DB in which we need to use some very different languages together (Ukranian, Bulgarian, Romanian, Italian (Italy and Swiss), English).
We already have a DB in use for Italian.
My first thought was to split up the different languages in different DB's with different languages but that is NOT possible. Everything must fit in 1 DB (and 1 company)!

Does someone know which collation we can use that works for all?
And how we can change the current collation (Afrikaans, Basque, Catalan, Dutch, English, Faeroese, German, Indonesian, Italian, Portuguese) to that collation?

davmac1

I changed the collation in Navision's alter database and it changed the collation for all existing objects.
(I made a backup first just in case.)
Set single user and save.
Then change collation ande save.
Then uncheck the single user.

As far as which collation to use - maybe someone else has a good idea.

kine

kriki wrote:

I searched for this but I didn't find anything conclusive.

We have 1 SQL DB in which we need to use some very different languages together (Ukranian, Bulgarian, Romanian, Italian (Italy and Swiss), English).
We already have a DB in use for Italian.
My first thought was to split up the different languages in different DB's with different languages but that is NOT possible. Everything must fit in 1 DB (and 1 company)!

Does someone know which collation we can use that works for all?
And how we can change the current collation (Afrikaans, Basque, Catalan, Dutch, English, Faeroese, German, Indonesian, Italian, Portuguese) to that collation?

I am afraid that best will be to use English collation and not use the local characters... but it depends on how the data are used. Do not forget that in case of different codepages, you can mess data if you open the database with different settings....

kriki

We also forwarded this to MS to hear if they had an answer.
They had 2:
1) use English for all companies and avoid local characters

2) use a different DB for the companies.

Let's see what we can do with those answers.......