Options

Error trying to drop keys

JWdeWJWdeW Member Posts: 3
edited 2007-03-02 in SQL General
hi,

when trying to disable keys on a table this SQL error appears:

Explicit @itemtype 'INDEX' is unrecognized (0)

Anyone seen this before or knows what it is about? It's in a turkish 3.70 database.

Any thoughts are appreciated.

Comments

  • Options
    krikikriki Member, Moderator Posts: 9,096
    [Topic moved from Navision forum to SQL General forum]


    The first topic I move to the new forum! :mrgreen:
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • Options
    kinekine Member Posts: 12,562
    JWdeW wrote:
    hi,

    when trying to disable keys on a table this SQL error appears:

    Explicit @itemtype 'INDEX' is unrecognized (0)

    Anyone seen this before or knows what it is about? It's in a turkish 3.70 database.

    Any thoughts are appreciated.

    May be that there is field with name INDEX in the key and it create problems with keyword INDEX on SQL?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    kriki wrote:
    [Topic moved from Navision forum to SQL General forum]


    The first topic I move to the new forum! :mrgreen:

    Well I suppose now you need to search for SQL threads and move them all. Looks like a fun weekend you have ahead. :mrgreen:
    David Singleton
  • Options
    krikikriki Member, Moderator Posts: 9,096
    kriki wrote:
    [Topic moved from Navision forum to SQL General forum]


    The first topic I move to the new forum! :mrgreen:

    Well I suppose now you need to search for SQL threads and move them all. Looks like a fun weekend you have ahead. :mrgreen:
    It will take more then that. I really have little time.... :cry:
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • Options
    JWdeWJWdeW Member Posts: 3
    I'm a little further ... it has to do with sp_rename on sql server not happy with the collation used: Latin-1 dictionary sort order, code page 1254, case-insensitive, accent-sensitive (130)

    When dropping an index other than the last Navision uses sp_rename to set index $4 to $3 and $5 to $4 etc. This is where it's goes wrong.

    Work around is to drop all and enable the ones needed...
Sign In or Register to comment.