Forum Discussion
Improvement to support for filtered indexes
Considering the following code works: CREATE TABLE TableName (ColumnName varchar(10))
CREATE INDEX IndexName on TableName (ColumnName)
ALTER TABLE TableName alter column ColumnName varchar(11) -...
This seems like an arbitrary failure. The indexing structure has not changed by increasing the varchar
Brett_Shearer , there is no failure on database side, with change the column data type (size), the index structure would change; therefore you get the error message. The enigne behaviour is absolutley correct.
olafhelper What index structure changes? AFAIK the maximum length of the field is not written on the nodes in the index (considering the field is varchar). This feels like a missing optimisation.
I'm just about to whip out dbcc page to see what is actually different on the index page - I suspect nothing.