Server and column collation conflicts in properties of a login

Problem:

Error: Cannot resolve the collation conflict between “Danish_Norwegian_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the UNION operation. (Microsoft SQL Server, Error: 468) when clicking “Securables” in properties of a server login.

Setup:

Server is set up with collation: SQL_Latin1_General_CP1_CI_AS
The database, or more precisely, the columns are created with collation: Danish_Norwegian_CI_AS
Login is set up with default language: English

The following steps will reproduce the error:

1. See properties for the server-login:

2. Click “User Mapping”

3. Click “Securables”

4. Observe error:

Cannot resolve the collation conflict between “Danish_Norwegian_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the UNION operation. (Microsoft SQL Server, Error: 468)

Solution/Impact:

Can anyone say anything intelligent about this issue?

 

 

 

 

This entry was posted in Programming and tagged , , , . Bookmark the permalink.

2 Responses to Server and column collation conflicts in properties of a login

  1. You have to tell SQL Server what collation to use explicitly (add a COLLATE clause).

    You can find the reasons for this particular error in a SQL Server Central post:
    http://www.sqlservercentral.com/articles/T-SQL/61288/

    • Jens Vestergaard says:

      Hi,
      Your suggestion is correct, if I was to have the problem in the context of a query.
      In my case, however, there is no way to force the collation, since it’s done behind the scene by Management Studio

      Best regards
      /J

Leave a Reply