Post reply

Case-sensitivity of login names

  • July 30, 2007 at 9:41 am

    #179918

    Hello there,

    I am wondering, why SQL Server 2005 (9.0.3042) behaves differently on two separate installations.

    On both machines I have defined logins, which have upper-case names ("TESTLOGIN"). I can connect to the databases using the correct names, but on one machine I also can connect using the lower-case representation ("testlogin"). The other server does not accept the lower-case login name.

    • Both logins are created using SQL Server authentication.
    • Both machines use Windows 2003 Server.
    • The connections are made using the JDBC driver of DataDirect (Connect for JDBC 3.7).
    • The same application (same client machine) is used to connect.

    Does anyone have an idea, why that is?

    I highly appreciate an explanation of this behavior.

    Thank you,

    slowjoe

  • July 31, 2007 at 3:42 am

    #723513

    Hi Slowjoe,

    Check the collation for both servers, it sounds like one of them could be case-sensitive.  If you right click over the instance in EM and select properties you'll see the collation on the general tab.  Eg. SQL_Latin_General_CP1_CS_AS - the CS means case sensitive.

    Cath

  • July 31, 2007 at 3:55 am

    #723518

    Thank you, Cath!

    That is correct. The server collations are different:

    • Latin1_General_CS_AS (only the correct case works)
    • SQL_Latin1_General_CP1_CI_AS (both cases work)

    Thanks again for the explanation!

    Regards,

    slowjoe

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply