Some tables are metatables involving data/information connected to the software releases. The Source Control utility should have a possibility of setting a switch on the tables, turning data compare on. This way you could include data for these tables in the version control.

For procedures/packages etc. it would be great to be able to have a "script as CREATE OR REPLACE" option.

We would use this to generate scripts that could be kept under source control in Mercurial, and applied to the (shared) dev database as needed.

We could also then use the tool to compare whether the database is up to date with the latest changes in source control.

With a maven plugin developers could easily automate deploys. The plugin should be configureable, but include the possibilites of first pulling from a developer database into svn. Then pushing the changes from svn (including other changes registered in SVN) towards a deploy test database.

When creating documentation in Schema Doc, I'd also really like to document tables and column comments.

We manage ERP systems with larg schemas (150.000 - 200.000 objects) where only a small proportion - the custom objects - should be under source control / schema compared.

To enable a decent use of Schema Compare for these systems, we would need to be able to compare schemas partially based on naming convention. Multiple assignments per schema should be possible, e.g. we want to match all objects for schema ABC matching the naming convention EE% and FF%

It seems materialized views are not included in the compare. Or am I missing something?

Could you please make it possible to compare tables with different tablenames?

This should be applied to all tools.

I do believe this is possible in the SQL Server-tools.

We frequently bring data from production databases to staging and development environments, it involves around 120 tables , but to start with we want to pick 3 or 4 huge tables(rows ~ 3 million) and see how much time it will take to do data comparison and deploy differences, instead of copying down entire tables.Also please see if you can develop the functionality of selecting a list of tables for comparison before registering entire databases.

If a column is renamed, Schema Compare for Oracle sees this as a drop and create, so during the table rebuild data is preserved asides from the “new” column.

Could you make this work similarly to SQL Compare and execute a rename instead?

Generate a script that contains all the synonyms that have been created to support the schema being version controlled.

When working on an object, we would like to see an option to check-out and/or lock the item it is mapped to in source control. Preferably, we would like this to happen when the item is edited and compiled. Again, this could be an XML config file option of some kind, or an option during check-in to lock the file for the user checking it in.

If changes can occur in both the source and on the database directly, it would be helpful to know which was updated last and when.

We noticed that all objects have a prefix in front of it.
The prefix happens to be the same as your folder name. I would prefer it if it was the same as the schema name, or NULL. Preferably give us the right to choose a prefix name.

as SQL Schema compare sdk