Altering SQL collation sequence

We currently have a Navision 3.01B SQL database with collation sequence ‘Western-European dictionary order, code page 1252, case-insensitive, accent sensitive (52)’, and are thinking of changing it to be ‘Binary Sort Order, code page 437 (30)’. The reason for this, is to get some Chinese (PRC) characters to echo correctly when they are typed into Navision fields. Most Chinese characters display correctly, but a few (3 known at the moment), do not. Does anyone know of any issues we may encounter if we do this? Performance, or sort orders changing, or anything else? Thanks, Andy

Performance, no problem (meaning no degradation) - binary is actually slightly faster per character compare than a dictionary order, though not really noticeable on the whole. The sort order will of course changes, and since you are storing double byte chars in a binary order you should check before hand that the sorting makes sense for Chinese. A similar test I was involved in with Japanese gave a pretty good sorting and the characters that utilised double byte were grouped in a reasonable way. In that instance it was code page 850. I am curious as to how you intend to do the conversion, since on SQL Server this task is actually quite difficult (and very length for large databases). Navision 3.70 allows you to change Collation (and handles the difficulty), so perhaps you’re going that route… Good luck.