June 11, 2006 at 8:46 am
I recently became the dba for a company and I am in the process of analyzing their sql setup. I have always worked with databases where the server collation and database collation is CI (case insensitive). However I think I am finding that the collation is not set up to be case insensitive on a particular server.
The server and database collation on this one particular server I am referring to is Latin1_General_BIN. When I execute the following statement "select * from master.dbo.sysdatabases" I get results returned as expected. However, if I run the "SELECT * FROM MASTER.DBO.SYSDATABASES", I get "Invalid object name 'MASTER.DBO.SYSDATABASES'."
I have checked the server collation of my other servers that have sql server set up on and the server collation is SQL_Latin1_General_CP1_CI_AS and they of course do not have a problem with the uppercase etc..
My question is, since the server and database collation does not specify CI for case insensitive, but rather BIN for binary sort order, is this the reason for the case sensitivity I am experiencing on that particular server?
I appreciate all feedback for any help received on this matter.
Thanks.
JWA
June 11, 2006 at 12:34 pm
The binary osrt order is case sensitive and will be why you are seeing the difference.
David
June 13, 2006 at 6:59 am
Binary sort order is case-sensitive, that is lowercase precedes uppercase, and accent-sensitive. This is the fastest sorting order.
If this option is not selected, SQL Server follows sorting and comparison rules as defined in dictionaries for the associated language or alphabet. - BOL
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply