Post reply

SQL Server 2005 Case Sensitivity

  • August 29, 2008 at 2:31 am

    #93854

    Any of you have any idea why SQL Server 2005 is having CASE Senstive Schemaname.tablename collection.

    Let say i am having Schema Person in which i am having table Contact,

    then person.contact will never work, you will have to enter it as according to you declared Person.Contact. (with a default installation)

    Regards,

    Manoj

  • August 29, 2008 at 2:57 am

    #864888

    Hi

    Check the collation of your server and database.

    "Keep Trying"

  • August 29, 2008 at 4:11 am

    #864909

    Thanks for reply chirag.

    I have used the word "default" in the question.

    Regards

    Manoj

  • September 4, 2008 at 6:43 pm

    #867518

    Sounds like SQL Server was setup with Binary Sort as the default collation. I would also bet that all your column names, table names, etc are case sensitive as well. Also, all queries that use the default sort would also be case sensitive.

    Binary Sort is a pain until you get used to it. Then it just becomes second nature. 🙂

    Gary Johnson
    Sr Database Engineer

  • September 5, 2008 at 4:27 am

    #867647

    i mean to say comparing with SQL 2000

    selecting serverproparty('collation') will return defaulr SQL_Latin1_General_CP1_CI_AS (if i am not wrong).

    but As 2005 introduce Schema feature which becomes

    Case-Sensitive combination of schema and tablename.

    which becomes more tedious job then earlier.

    Regards

    Manoj

Viewing 5 posts - 1 through 4 (of 4 total)

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