Results 1 to 8 of 8
  1. #1
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941

    Unanswered: Case Sensitive Object Names?

    My new DB seems to be "case-sensitive". I have a table named Bld_List.

    Select * From Bld_List

    returns all records in QA. However, if I don't follow the correct case

    Select * From bld_list

    I get this error: Invalid object name 'bld_list'.

    Also, when I try to get rid of some unnecessary records by using this

    DELETE
    FROM Bld_List
    WHERE (PRODUCT IN
    (SELECT DISTINCT Product
    FROM BldOff_Inv_Daily))

    I get this error: Cannot resolve collation conflict for equal to operation.

    I imagine I set something up wrong when I first built the DB, but I don't know what to look for.

    Thanks
    Inspiration Through Fermentation

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    I'd suspect you are not using the default character set collations. Character sets can be either case-sensitive or case-insensitive, and I think this applies not just to the data but to the object names as well.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  3. #3
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941
    So is that something I can change?

    I used the Collation Name that my other databases are set to:
    SQL_Latin1_General_Cp1_CI_AS
    or is it some other setting?
    Inspiration Through Fermentation

  4. #4
    Join Date
    Jan 2005
    Posts
    28
    Hi,

    CI is pointing that the collation is Case Insensitive.

    If you take a create script of your tables, you can see if a non-default collation is used.


    Eralper
    http://www.kodyaz.com

  5. #5
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    What does sp_helpsort tell you?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  6. #6
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941
    Quote Originally Posted by eralper
    Hi,

    CI is pointing that the collation is Case Insensitive.

    If you take a create script of your tables, you can see if a non-default collation is used.


    Eralper
    http://www.kodyaz.com
    hmmm...
    [PRODUCT] [varchar] (16) COLLATE SQL_Latin1_General_CP1_CS_AS NOT NULL

    Do I need to rebuild and repopulate the table? I only have a few so far, so it wouldn't be a huge deal.
    Inspiration Through Fermentation

  7. #7
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941
    Quote Originally Posted by Brett Kaiser
    What does sp_helpsort tell you?
    Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data
    Inspiration Through Fermentation

  8. #8
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941
    Ok, I think I've got it. I did change the collation at some point over the weekend. Any tables I created after that are okay.
    If I just use the Alter Table Collation clause on the first tables I created, that should take care of the problem, right?
    Last edited by RedNeckGeek; 03-19-07 at 12:02.
    Inspiration Through Fermentation

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •