Comments
3 comments
-
We've had other requests for this. The problem at the moment is that SQL Compare treats columns as part of the table definition rather than entities in their own right. However, your feedback has been noted and we'll hopefully work out how to solve this in a future version.
David Atkinson
Product Manager
Red Gate Software -
This would be a very welcome addition to the SQL Compare feature set!
Any plans to add it in the future? (I see that the original posts in this thread were written three years ago...)
/Mattias -
We're improving the handling of columns in the next release by allowing renamed columns to be mapped to each other. But other than the existing behavior of ignoring columns in comparison, there are no further improvements planned for the immediate future.
David Atkinson
Red Gate Software
Add comment
Please sign in to leave a comment.
The reason for this, is I have two versions of a database and I want to add a new feature to BOTH but the schema and data is not 100% identical.
For Example:
Now I want to add Field5 to both so they would look like:
Right now the way it works, if I was to Sync in either direction, I wouldn't get the result I wanted.
Syncing A --> B would result in Field3 being copied to Table B, which I don't want.
Syncing B --> A would result in Field3 being removed, which I don't want.
It would be nice if you allowed me to turn off the syncing of Field3.