AlwaysOn & Contained Databases Collation Conflict RRS feed

  • Question

  • Here is my situation.

    I have setup an alwaysOn availability group which is working fine.

    In this AlwaysOn availability group I have converted the Adventureworks database to a contained database. I also added a Contained User.

    Connecting to the secondary "Contained" database was no problem.
    But here is my problem, when expanding the tables I received the following errormessage:"Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement column 3."

    Doing this action on the primary is no problem. Executing a select statement against the secondary is also no problem and returns a result.

    After some trial and error, I’ve seem to fixed the issue by doing a failover to all my secondary databases.
    After, expanding the tables to the primary & secondary worked.

    Does anybody have an idea why this happened, and am I the only one experiencing this issue?

    Thanks, Bram

    Thursday, September 11, 2014 9:50 AM