Cannot resolve collation conflict for equal to operation.
In MS SQL SERVER, the collation can be set at the column level. When compared to 2 different collation columns in the query, this error comes up.
SELECT ID FROM ItemsTable INNER JOIN AccountsTable WHERE ItemsTable.Collation1Col = AccountsTable.Collation2Col
If columns ItemsTable.Collation1Col and AccountsTable.Collation2Col have different collation, it will generate the error “Cannot resolve collation conflict for equal to operation“.
To resolve the collation conflict add the following keywords around “=” operator.
SELECT ID FROM ItemsTable INNER JOIN AccountsTable WHERE ItemsTable.Collation1Col COLLATE DATABASE_DEFAULT = AccountsTable.Collation2Col COLLATE DATABASE_DEFAULT
Watch this quick video for resolution:
Collation can affect the following areas:
- Where clauses
- Join predicates
- Functions
- Databases (e.g. TempDB may be in a different collation database_default than the other databases some times)
Checkout following video how collation can change the order of the column:
Just like collation, there is another problem with SQL Server and that is related to Parameter Sniffing, I have written a detailed blog post about how the parameter sniffing can be resolved in SQL Server.
Here are some really good blog posts which you can read about parameter sniffing and how you can avoid the problem related to it.
- SQL SERVER – Parameter Sniffing Simplest Example
In this blog post, we discuss what actually is parameter sniffing and how we can overcome it with the help of recompiling the stored procedure. - SQL SERVER – Parameter Sniffing and Local Variable in SP
It is easy to overcome the parameter sniffing for the stored procedure by declaring the local variable inside the stored procedure. - SQL SERVER – Parameter Sniffing and OPTIMIZE FOR UNKNOWN
You can take advantage of the new query hint of Optimize For Unknown to simulate the local variable in the stored procedure. A very underutilized technique indeed. - SQL SERVER – DATABASE SCOPED CONFIGURATION – PARAMETER SNIFFING
This new database level enhancement was introduced recently which can help you overcome any issue with the parameter sniffing. - SQL SERVER – Parameter Sniffing and OPTION (RECOMPILE)
The oldest and most traditional technique to not cache the query plans and compile your stored procedure or queries every single time to get optimal performance. - Performance and Recompiling Query – Summary
This post summarizes the entire series of parameter sniffing, performance and recompiling query.
Reference: Pinal Dave (https://blog.sqlauthority.com)
381 Comments. Leave new
The error message is useless to help us know this is what we should do. But your tip is perfect. Thanks for the help.
Thanks a lot!
Hi!!!
How can i use the COLLATE DATABASE_DEFAULT in this update
update a set area = b.area from tbl_lnventas as a
inner join [10.105.162.223].dbunica3.dbo.cat_entidad as b on b.codigolada = left(a.ctelefono,8)
where a.area=”
go
Great solution. Solved my problem.
Thanks a lot!!!
Worked for me :)
Hi i need a help with collation problem
I am creating a database with sql_latin_general collation in an sql instance with collation latin_general.
While running installed application error occurs.is there any way to handle this scenario.
Please help me its very urgent
Thanks a lot.
It has saved lot of our time.
Whew Superb!!!
Thanks Pinalkumar, worked a treat for me.
Thank God for forums and the people like you who give their expertise so freely and unselfishly.
Thanks a lot.
It was very helpful for me.
This work , very helpful to you
It Realy Works !!!
Thanks
Thanks from me too!
Gracias, muchas gracias.
thanks admin
Gosh, thanks. I hate this problem and I always forget the solution, so finally I’ve bookmarked this page.
You’re a life saver. Nice to see a 2 year-old blog post bring satisfaction to so many!
I just saw this and, from an educational perspective, want to say that the original statement at the top of this post has a syntax error in that it is missing the ON clause and therefore won’t compile.
Having said that, the information contained therein was useful.
Tony S.
Excellent solution!!! this helped me to fix my problem
Thanks, It solved my problem
hi i was wondering if you can help. I am testing a script in SQL server 2000 (Query Analyzer) and everytime i am doin a runtime it gives me the following error:
Cannot resolve collation conflict for equal to operation.
my code is this
select Count(distinct username) as Failed from
(select Quiz.quizId,QuizAttachment.nodeID
from Quiz,QuizAttachment,PolicySet
where Quiz.quizID=QuizAttachment.quizID
and QuizAttachment.nodeID=PolicySet.nodeID
and Quiz.active=1)PartialQuizDetails
any idea on how to resolve this? would most appreciate it
oh and have to mention that my collation on my database that im using is on SQL_LATIN_GENERAL_CP1_CI_AS
@Simar
One issue is that the COUNT works on username, which is not a field in the SELECT clause of the sub-query.