Error: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_100_CS_AS" in the equal to operation. - Fixed
![EDA tables cannot be joined with two different collations against SQL Server: A Solution - The Rocket MultiValue Blog EDA tables cannot be joined with two different collations against SQL Server: A Solution - The Rocket MultiValue Blog](https://blog.rocketsoftware.com/multivalue/wp-content/uploads/sites/8/sites/8/2019/04/EDA-Blog2.png)
EDA tables cannot be joined with two different collations against SQL Server: A Solution - The Rocket MultiValue Blog
![sql server - index not being used due to different collations - is there any work around? - Database Administrators Stack Exchange sql server - index not being used due to different collations - is there any work around? - Database Administrators Stack Exchange](https://i.stack.imgur.com/bXSDl.jpg)
sql server - index not being used due to different collations - is there any work around? - Database Administrators Stack Exchange
![Collation Matters – Few things to note when thinking your Server's or database's collation and easy tool to test collations - Blog Collation Matters – Few things to note when thinking your Server's or database's collation and easy tool to test collations - Blog](https://www.qumio.com/Blog/Lists/Photos/051614_0952_CollationMa5.png)