Warehouse Manager 200 Technical Bulletin: TB200-16
SQL Collation Sequences
Compatibility: WHM200 / IM200
SQL Collation Sequences for Sage 200
Datalinx In line with Sage's recommendations regarding thei BI package and Sage 200 Datalinx also recommend that Inventory Manager 200 and Warehouse Manager 200 follow the same resolutions with the collation sequence for Sage 200 databases.
The recommended collation sequence for Sage 200 databases is:
“Latin1_General_CI_AS”
Issue no. 4437: Customer receives the following error when trying to refresh BI Cube (or create a new Data Warehouse): “Error 468 : Cannot resolve the collation conflict between ‘SQL_Latin1_General_CP1_CI_AS’ and ‘Latin1_General_CI_AS’ in the equal to operation.”
This looks to be due to 2 different causes:
1) The Collation of the main Sage 200 database is set to ‘SQL_Latin1_General_CP1_CI_AS’, instead of the recommended ‘Latin1_General_CI_AS’.
2) The Collation of the Sage 200 / BI databases are correct but the overall Collation held against the SQL Server instance is set to ‘SQL_Latin1_General_CP1_CI_AS’.
Reason: The Collation of a database can be compared to a language and when the program finds 2 databases with different collations it is like comparing English to Chinese. The problem seems to have surfaced with v2011 SP1 as we are now using more temporary tables and, especially in point 2) above, these temporary tables will be stored in the TempDb system database which uses the Collation from the overall SQL Server instance.
For further information please contact your account manager or email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Please log in to see previously published Datalinx Technical Bulletins and customer support documents.