Has anyone else seen this? I've googled this, but there seems to be no reason "why" so far. And that's what I'm trying to find, the reason why this happens. I've already got a work around.
Running the following query:
..comes up with the below error message:
Now, as none of my databases, System DBs included, are set to "Latin1_General_CI_AI", I cannot think as to why SSMS would be trying to do a conversion from the _AS collation to the _AI collation. Nothing in my query requests a collation conversion and it shouldn't have.
As I said above, I have a workaround I found here: but my question is, why should I have to use a work around? Why won't it work as written?
If anyone has any specific knowledge or random thoughts you'd like to share on this issue, I'd love to hear them.
Thanks,
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
Running the following query:
Code:
USE MyDB
Select o.[name] as TableName,
Case When e.[value] is Null or e.[value] = ' ' Then 'Table Descrip N/A'
When e.[value] is not Null Then cast (e.[value] as varchar (3000))
End as TableDescription
from sysobjects o with (nolock)
left join
::fn_listextendedproperty('MS_Description','user','dbo','table', default, null, null) e
on o.[name] = e.objname
where o.xtype = 'U' --and
--o.[name] = LTrim(RTrim(@tblName))
Order by o.[name]
..comes up with the below error message:
SSMS Error said:Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Now, as none of my databases, System DBs included, are set to "Latin1_General_CI_AI", I cannot think as to why SSMS would be trying to do a conversion from the _AS collation to the _AI collation. Nothing in my query requests a collation conversion and it shouldn't have.
As I said above, I have a workaround I found here: but my question is, why should I have to use a work around? Why won't it work as written?
If anyone has any specific knowledge or random thoughts you'd like to share on this issue, I'd love to hear them.
Thanks,
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"