I asked this question about SQL Compare 9, and the response was "hopefully we can implement it in a future version."
http://www.red-gate.com/MessageBoard/vi ... hp?t=13834
Basically, we would like to compare our development database with our production database, synchronize primary keys, unique constraints, and unique indexes, and ignore non-unique indexes.
Primary keys, unique constraints, and unique indexes are functionally significant, are created by the developer on the development database, and need to be deployed to production.
Non-unique indexes only affect performance, are maintained by an administrator directly on the production database, and must not be created or dropped just because they don't match what's in development.
So, is there any chance that SQL Compare 10 will compare unique indexes and ignore non-unique indexes?