An issue was found with Sage 200 BI when Sage 200 2011 SP1 was released. The problem related to the SQL collation settings on either the Sage 200 Database or the SQL Server instance. A hotfix has now been released for Sage 200 2011 SP2 to fix this problem.

It should be noted that the SQL collation for Sage 200 SHOULD be Latin1_General_CI_AS.

Details from Sage, about the fix are below.

Overview
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 database 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.
 
This file will fix both sets of issues.
 
Prerequisites
The customer must have upgraded to Sage 200 v2011 SP2.
The Sage.BI.Database.SQL.dll file will need to be copied onto each Client machine.
[Note: The new File version will become 16.0.12019.4]Note: This file needs to be copied to the folder path C:\Program Files\Sage\Sage200
This is confirmed within the “Installation guide for v2011 SP2 Hotfix 3.doc” within the Zip files.Noticeable Changes to the Application:No changes.

Advertisements