Fix bug with Change Tracking
There is a bug with change tracking on both SQL Source Control and Schema Compare. When a script is generated to alter a table that has change tracking already enabled, the ENABLE CHANGE_TRACKING script is added to the script causing the whole script to fail because change tracking is already enabled. This bug has been there for a long time. This bug is making both products difficult to use. It has been reported multiple times but has not been fixed yet.
SQL Source Control 3.0 is now available which includes a fix to this issue.
For more information about the release, please see:
An Early Access build of SQL Source Control 3.0 is available which inlcudes a fix for this issue.
The installer zip can be found here:
As I said, this is an Early Acces build - so does not include all the functionality we are hoping to provide with v3.0 and will not be as stable as the full release (which will be available later in the year). However, we'd really like to hear feedback from you regarding whether this solves the problem you've described.
SQL Source Control v3.0 major new feature is called "SQL Migrations". This feature will help avoid data loss when renaming a table as it allows you to create, store and share SQL migration scripts for accurate deployment.