none
Can not resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation RRS feed

  • Question

  • Hi,

    We have upgraded from SQL Server 2008 to SQL Server 2017. But one of the application is getting below error-

    Can not resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

    Please let us know the reason of the issue and solution for this.

    Regards

    Arif

    Saturday, June 22, 2019 5:01 AM

All replies

  • Hi arifulhaq,

     

    >>Can not resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

     

    SQL Server allows  users to create databases, tables and columns in different collations. If there is a mismatch of two collations in database, errors come up.

     

    Would you please check the collation of tables accessed by the application, especially the joined columns.

     

    Hope this could help you .

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, June 24, 2019 9:52 AM
  • We have upgraded from SQL Server 2008 to SQL Server 2017. But one of the application is getting below error-

    Can not resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

    Please let us know the reason of the issue and solution for this.

    It seems you may have installed SQL Server 2017 with different collation than the original SQL Server 2008 instance. A common cause of collation conflict errors in this scenario is that tempdb objects use the instance collation, resulting in errors when user and tempdb database objects are joined.

    One solution in this case is to reinstall SQL Server 2017 with the same collation as the SQL 2008 instance. Another solution, which requires T-SQL code changes, is to explicitly specify COLLATE DATABASE_DEFAULT for tempdb object columns so that the collation of the current user database is used instead of the instance default collation.


    Dan Guzman, Data Platform MVP, http://www.dbdelta.com

    Monday, June 24, 2019 10:48 AM