Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Yes, this is the result of a case-sensitive collation on the server where your views are located. </p> <p>And it's why I always grouse about having case-sensitive collations at the server level directly (instead of just using collations at the column-level) as I pointed out here: <a href="http://www.sqlmag.com/blog/practical-sql-server-45/tsql/Collation-SQL-Server-139576" rel="nofollow">http://www.sqlmag.com/blog/practical-sql-server-45/tsql/Collation-SQL-Server-139576</a></p> <p>Only, in trying to wrap my brain around how you'd cram a COLLATE clause into a distributed query, I figured there had to be a better way. </p> <p>And, it looks like you can set some specific options as part of your linked server's definition: <a href="http://msdn.microsoft.com/en-us/library/ms191145.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms191145.aspx</a> As that defines how to specify collation options when working with Collations in Distributed Queries. </p> <p>The issue, however, is that you'll need to use a linked server instead of allowing ad-hoc distributed queries (but they're a security risk/concern anyhow). So I'd recommend using a Linked Server as a better approach anyhow. </p> <p>Try this link as well - as it provides details on how to control collation settings on the linked server: <a href="http://msdn.microsoft.com/en-us/library/ms186839.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms186839.aspx</a></p> <p>And, of course, I'd recommend changing the column name if at all possible.</p> <p>--Mike</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload