Not handling Clustered->Nonclustered index change

dave.novelli

I have made a change to my dev database where I changed the primary key index to nonclustered, and created a new clustered index on a completely different field.

Compare attempts to add my new clustered index without first altering the existing clustered index, and an error results.

I can certainly modify the update script manually to get around this - but is there something I'm not doing that would make this work correctly?

Thanks,
Dave