Case-sensitive collation affects T-SQL object names, not only data - by Dmitry Mashkov [MSFT]

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 336083 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/31/2008 4:00:43 AM
Access Restriction Public


If SQL is installed with case-sensitive collation, some queries to system objects become case sensitive which is fully unexpected.
Sign in to post a comment.
Posted by Dmitry Mashkov [MSFT] on 4/21/2008 at 3:50 AM
Can you point to the official documentation about this?
Posted by Microsoft on 4/14/2008 at 3:41 PM

This is behavior is actually by design as all system object names and type names are cast the system level collation. In the example stated, the names of the catalog views are in lowercase, so select * from TEMPDB..SYSOBJECTS will fail if the collation of tempdb is case sensitive. Queries must be written with the collation case sensitivity take into consideration. Hope this helps.

Posted by DB007 on 3/31/2008 at 4:49 AM
This has always been the case. This is per-design, this is expected behaviour.