JOb failed due to collation conflict

  • ramyours2003

    SSChampion

    Points: 12118

    We migrated the databases and jobs from sql 2005  to SQL 2016  and the collation of sql 2016  is "SQL_Latin1_General_CP1_CI_AS"  and sql 2005 is "Latin1_General_CI_AS"  and all the databases in sql 2016 is having the same collation SQL_Latin1_General_CP1_CI_AS", When we tried to run a job which is configured on master to check the database connections getting error as

    Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. [SQLSTATE 42000] (Error 468). The step failed.

     

    how to resolve this issue

     

  • John Mitchell-245523

    SSC Guru

    Points: 148360

    You'll need to change the collation of the databases or of the server (not a trivial task), or insert COLLATE clauses in your code.  You'll probably find you need a COLLATE clause wherever you join on character-based columns with different collations, or attempt a UNION involving character-based data with different collations.

    John

  • ramyours2003

    SSChampion

    Points: 12118

    You'll probably find you need a COLLATE clause wherever you join on character-based columns with different collations, or attempt a UNION involving character-based data with different collations?

    How can we do this

  • John Mitchell-245523

    SSC Guru

    Points: 148360

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply