Mixing different codepages (ex. Mexican, Thai, Taiwanese (Chinese) and Danish) in one Navision/NAV4.00 SQL Server 2005 database is sure possible. And it actually works fine. As long as we stay internally in NAV.
But what when we want to integrate to other applications?
In my company we have the following setup: NAV4.00 SP3, SQL Server 2005 and Reporting Services. The problem is that since the characters for ex. Thai are not saved using SQL Servers native codepages, then they don’t display correctly in Reporting Services. The interface between our Data Store used by Reporting Services and our NAV SQL database is SSIS (SQL Server Information Services).
Do you know of any way that we can “translate” these codepages into “native” SQL codepages and this way have data displayed correctly in SQL?