Collation change -> filtered indexes ignored

anke.jageranke.jager Posts: 2
edited December 1, 2016 6:45AM in SQL Compare
When the collation of some columns changes, all of the (unique) indexes they are used in, are dropped and recreated, except for the filtered (unique) indexes. These indexes seem to be ignored, resulting in an error during deployment:
Msg 5074, Level 16, State 1, Line 166
The index '<index_name>' is dependent on column '<column_name>'.
Msg 4922, Level 16, State 9, Line 166
ALTER TABLE ALTER COLUMN <column_name> failed because one or more objects access this column.

I have SQL Compare 12.0.33.3389 installed.

Comments

Sign In or Register to comment.