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...
Comments
The first topic I move to the new forum!
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
May be that there is field with name INDEX in the key and it create problems with keyword INDEX on SQL?
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Well I suppose now you need to search for SQL threads and move them all. Looks like a fun weekend you have ahead.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
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...