One of the most common errors database developer’s receives when they start working with database where there are different collation used. Collation is a very important concept but it is often ignored. First use the method displayed in this video to resolve your error and right away put your efforts to understand what collation stands for. The error message says SQL Server cannot resolve the collation conflict. Here is how to fix this collation conflict error quickly.
Language is the most important part of communication. We all communicate with each other through language which both persons to understand. If we do not talk in the language which the other person cannot understand, the end result is not fruitful. In a similar way, collation is very important to any database. I have often seen situations when the collation changes from case sensitive and case insensitive turning the query result hey-wire and creates chaos on the server.
Let us see the same concept in following SQL in Sixty Seconds Video:
Related Tips in SQL in Sixty Seconds:
- Effect of Case Sensitive Collation on Resultset
- Collation and Collation Sensitivity – Quiz – Puzzle – 6 of 31
- Detecting Database Case Sensitive Property using fn_helpcollations()
- Cannot resolve collation conflict for equal to operation
- Find Collation of Database and Table Column Using T-SQL
- Collate – Case Sensitive SQL Query Search
What would you like to see in the next SQL in Sixty Seconds video?
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
1 Comment. Leave new
we have used #temptable in so many procedure of mydb with join condition & collation of mydb and tempdb are different.
now I want to continue with mydb collation but can’t change collation of tempdb
what can i do?