SQL Server 2008 R2 on Server 2008 R2 "iron".
Within the last 2 weeks a database that is set (collation...) as CI, on a server that is CI, looking at a view that is CI, is suddenly CS in it's behavior. In other words, I cannot see any level where it is, indeed, CS yet it is acting that way. The entire query (and, again, it's a view):
select
avg(value)as'Avg'from analoghistorywhere [datetime]>='02/09/2014'and [datetime]<='02/09/2014 23:59:59'and tagname='Digester1.AverageTemp'
The 'TagName' "column" of the view is the one that's suddenly case sensitive. If any of the letters' case is not exactly as above, it returns 'NULL'. Column names still appear to be CI as those in the query are NOT in the proper case. I can use "like" and it works, but I'd rather figure out what happened and straighten that out as I have several Excel macros using this same view and I don't want to have to find them all and "fix" them.
I have even attempted forcing the collation by adding "COLLATE
SQL_Latin1_General_CP1_CI_AS" to the query but I still get "NULL" as a query result
