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

hmm , I got this error when doing some database things today.

 It appears that db1 is of collation SQL_Latin1_General_CP1_CI_AS and

db2 is of Latin1_General_CI_AS and when i do a select from both database, it give me the above error.

How to solve it:

1. Change to single-user mode in your database

2. Change the collation of db2 from Latin1_General_CI_AS to SQL_Latin1_General_CP1_CI_AS

3. Drop and re-create those tables which are still using collation Latin1_General_CI_AS in their columns.

 This step is necessary cos although u change the collation at the database level , the table level is still sticking to the previous collation

4. Restore the data of those tables.

 OR u got to specify which collation to use in your sql statements,

like

select top 10 * from torversrv03.torver_ukug.dbo.registrations r inner join #test t on t.title = r.fullname

COLLATE SQL_Latin1_General_CP1_CI_AI

I know this sucks...no wonder dba get paid so much these days...lol

Published Friday, November 17, 2006 8:11 AM by darenhan

Comments

# re: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.

Tuesday, November 21, 2006 10:54 AM by darenhan

I found out I can change the collation at the column level in the tables but sometimes they will change back to the old collation. It is kinda of strange....

# Hugh

Tuesday, July 29, 2008 7:49 AM by Grady

bb97db72cb21aa5ee98203c1d01be7b2

<a href="njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2">">njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2"> njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2 </a>

njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2

[url]njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2[url]

Powered by Community Server (Commercial Edition), by Telligent Systems