Having bought SQLCompare for my client a few months ago but not had a reason to use it in anger until now, I just spun it up assuming that comparing indexes would be a feature, and somewhat shocked that it's not!

Please do what you can to include it ASAP as it's so important to compare database indexing when trying to work out why one database is outperforming another.

Ian

must have feature

this is definitely a must have feature in redgate schema compare

We've merged several requests into this one, as they all request that Compare treat indexes as separate objects (with some minor variations). We intend to do some user research in this area in the next few months, at which point we'll try to email you about the feature.

We often have a requirement to create bespoke indexes in live databases, however currently a SQL Compare deployment will remove these indexes. It would be good if we could filter out certain indexes, or just prevent those in the destination database from being dropped.

I've just hit this very scenario myself, needing to merge optimisation changes back from a development to a production branch where the table schema has changed. I have to do it manually because otherwise I destroy the existing table schema before the changes are ready for production. This would be super super helpful.

When comparing tables, additions/changes in indexes are included as part of the differences to the table. I would like a way to separate index management from table management. In other words, it would be nice to be able to select a table for modification without including the indexes. I know we can do this from a project level with settings, but if there are many tables selected for change, I would like to be able to include the indexes for some tables and not others. Also, it would be nice to be able to select individual indexes on a given table. Sometimes multiple indexes would display for a given table and it would be nice to hand pick which indexes are being selected for promotion.

When one wants to build, rebuild or stage a database in a step-based fashion (like we often did in the old days with master scripts), it would be nice to leverage SQL Compare to aid in generating/deploying such scripts. The classic example is the desire to drop and re-add keys for data migration/ETL scenarios, so that one can TRUNCATE and bulk load. Currently, I maintain my own master scripts for this reason. So it would be nice, too, to propagate this into SQL Source control's tracking behavior, too!

Options to select what type of differences to deploy, e.g. data types, primary keys, constraints, foreign keys, indexes, ...