Home Dashboard Directory Help
Search

collation issue raised by a system UNION query looking at securables page of a user's properties. by jsmacc


Status: 

Closed
 as Fixed Help for as Fixed


7
0
Sign in
to vote
Type: Bug
ID: 336208
Opened: 3/31/2008 2:24:07 PM
Access Restriction: Public
Duplicates: 426075 521503
0
Workaround(s)
view
7
User(s) can reproduce this bug

Description

Cannot resolve the collation conflict between "Latin1_General_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the UNION operation. (.Net SqlClient Data Provider)

TITLE: Microsoft SQL Server Management Studio
------------------------------

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=468&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


Details
Sign in to post a comment.
Posted by PatLap on 7/13/2012 at 6:10 AM
The problem comes from the SSMS application. If you click direclty on securables when opening the login, the select to get the securables will be executed on master. But if you first go in the user mapping then on the securable tab, the same select is executed on the first DB of the list (alphabetical order). Therefore if that DB is not in the same collation than the server, you will get the error. SSMS is missing an USE statement to get back on master DB upon clicking on the securables tab.
Posted by Manee kantha on 6/7/2012 at 3:29 AM
I also have this issue with SQL Server 2008 R2 SP1.
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Finnish_Swedish_CI_AS" in the UNION operation.
Posted by DanaBa on 11/15/2011 at 11:49 AM
I also have this issue with SQL Server 2008 R2 SP1.

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

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

Is there any fix at this time? Do you know if this is affecting our servers in any other way - perhaps we have not come across it yet?

Thanks for the assistance.
Posted by Rebecca123 on 11/3/2011 at 6:36 AM
Issue is back with SQL Server 2008 R2:

Server Latin1_General_BIN, database Latin1_General_BIN2
Posted by Ana Mihalj on 9/6/2011 at 4:31 AM
Same error on SQLServer Denali CTP3.
On my server with different collation:
Cannot resolve the collation conflict between "Latin1_General_100_CS_AS" and "Croatian_CI_AS" in the UNION operation. (Microsoft SQL Server, Error: 468)
Posted by Microsoft on 7/25/2011 at 11:42 PM
Hi

Greetings from the SQL Server Manageability team.

We have fixed this issue. This will reflect in an upcoming release of SQL Server.

Thanks for providing feedback.

Regards,
Shilpi
Posted by georgescua on 1/19/2011 at 12:28 PM
Still happen identically on SQL2008

Microsoft SQL Server Management Studio                        10.0.2531.0
Microsoft Analysis Services Client Tools                        10.0.1600.22
Microsoft Data Access Components (MDAC)                        6.0.6002.18005
Microsoft MSXML                        3.0 4.0 6.0
Microsoft Internet Explorer                        8.0.6001.18975
Microsoft .NET Framework                        2.0.50727.4206
Operating System                        6.0.6002
Posted by Microsoft on 12/22/2009 at 12:08 AM
We are able to repro this defect:
Clear repro steps:

a.     Check the Server Collation : should be SQL_Latin1_General_CP1_CI_AS

b.     Create a login: abcd

c.     Create a database: someDb with collation: Latin1_General_CI_AS_KS_WS

d.     Create a user: abcd in database someDb and map it to login abcd

e.     Now open properties of login “abcd”.

f.        First open “User Mappings”.

g.     Now open “Securables”, you will get the same exception.


We will try to fix this by next major release.

Regards,
Sumesh
Posted by Microsoft on 4/1/2008 at 8:56 AM
Hi,

Thank you for reporting this problem. This problem cannot be repro'd using the latest SQL Server 2008 SSMS. Can you please download the latest CTP bits from http://connect.microsoft.com and verify out the same. I am marking this bug as Resolved/Not Reproducible. If you encounter this problem again, please reactivate this bug and attach the server and database collation settings and we will look into it.

Thanks
Karthik
MS SQL Server Team
Sign in to post a workaround.