Cause While older versions of SQL only allowed users to define the collation settings at the server level, SQL 2005 allows users to define the collation settings at many levels, such as the table and field levels. If the collation settings of these sub-levels are different from the collation settings at the server level, or the collation setting of the other server, collation errors will occur. This is only an issue with SQL 2005 servers.

Short Term Solution When using a SQL 2005 server to migrate GIFTS data from one server to another, clients should make sure that the new GIFTS database on the destination SQL 2005 server has the same collation setting as the GIFTS database from the source SQL 2000 or 2005 server (such as SQL_Latin1_General_CP1_CI_AS, which MicroEdge recommends).