Ability To Script Indexes and Foreign keys as seperate object scripts
It would be nice to be able to script indexes and foreign key constraints as seperate object scripts as the table columns may not change but may have additional indexes.
What an excellent idea
I'm more concerned about foreign keys than indexes. Foreign keys imply a build sequence that must be followed. If FK's are in a seperate script then they can be applied last.
Treating DRI foreign key constraints as seperate objects will permit tables to be created in any order and then have the foreign keys applied.