Hi,
I have a task that runs fine on my system and my UAT. However, on another server I get this error in Indicium;
"Cannot resolve the collation conflict between \"Latin1_General_CI_AS\" and \"SQL_Latin1_General_CP1_CI_AS\" in the equal to operation."'
I’ve check the collations on the servers, and both DB’s have the same collation; SQL_Latin1_General_CP1_CI_AS
But the server settings;
on the working server; SQL_Latin1_General_CP1_CI_AS
on the failing server; Latin1_General_CI_AS
Now, I see the difference, but I kinda expected Indicium to respect the Db’s collation settings. But I guess not? Also, I don’t think my client wants to change this on his uat server.
Is there any way to get around is?
Any help is appreciated!
Thanks,
Blommetje
Best answer by Vincent Doppenberg
View original