1
Vote

Changing index to a clustered index does not remove INCLUDE columns

description

When SQLAzureMW forces a change of an index to a clustered one (because it detects that there is no such index on a table; mandatory in Azure) it scripts the CREATE INDEX statement with the CLUSTERED attribute but does not take account of any INCLUDEd columns in the original non-clustered index. Thus an illegal statement is generated. Removing the INCLUDE parameter from the automatically generated T-SQL statement would resolve this. [SQLAzureMW v3.8.6 / SQL Server 2008 R2 10.50.2806]

comments

ghuey wrote Apr 24, 2012 at 5:04 PM

Hi Andy,

Very good catch, I will fix this right away.

Thanks very much,
George

ghuey wrote Apr 24, 2012 at 11:08 PM

Ok, this should be fixed in v3.8.7.

Regards,
George