How to solve SQL collation problem?

bastir

Hi,

I've developed a german solution in SQL database with SQL collation 52
(Western-European dictionary sort order, code page 1252, case-insensitive, accent-sensitive (52))

Now we have a international customer that needs SQL databaes with collation 82
(Latin-1 dictionary sort order, code page 1250, case-insensitive, accent-sensitive (82))

I tried to make a navision backup of the original database and imported it into the new database, everything was fine.
But when I tried to make a backup of the new database I got several errors:
Error 1190 in Modul 19

Furthermore the message tells me the table and the appropriate Key's.
When I look into the data of these tables I can see german umlaut/characters.
If I delete all of these values in the table the system goes on until it finds the next table with problems.

What did I wrong? Can anybody give me a solution how to deal tih these collation problems?

Thanks in advance

Sebastian

kine

In each case you need to have correct setting for non-unicode applications in the local settings of your windows. Before you restore the DB into DB with collation 82, you need to switch the language to English. After restore you can switch back.

kriki

[Topic moved from 'NAV 2009' forum to 'SQL General' forum]

bastir

kine wrote:

In each case you need to have correct setting for non-unicode applications in the local settings of your windows. Before you restore the DB into DB with collation 82, you need to switch the language to English. After restore you can switch back.

Do I've to change only before the restore?
I changed to EN-US before export and still get the same errors :-(

Best regards
Sebastian

kine

Main thing is that the language must be in line with collation with which you are working. But still, if there are characters in one DB, which doesn't exist in the second codepage, they will be mis-converted.