Compares and synchronizes SQL Server databases, backups and scripts.
Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong
Am I correct in the assumption that SQL Compare uses the database extended property "SQLSourceControl Database Revision" to determine what migration scripts are included in it's update script based on source control?
In other words it appears that you tie migration scripts to a specific change, and Compare references migration scripts as a solution to some problems or warnings it encounters.
What I'm aiming to do with clients who's database has never been part of a versioning system is to initially add this extended property and set the version to match nearly the first addition of the database to source control, then add migration scripts to the next version change so that SQL compare can be used to pull in all of these scripts in an effort to bring all client databases into a base starting point for versioning. I suspect I'll have to manually add the Extended property to start, and based on the compare update scripts I've looked at, manually increment the version after running a compare update.
- Posts: 1
- Joined: Thu Sep 12, 2013 4:12 pm
We're developing a new version of migrations that won't be tied to version control revision numbers. I would imagine that once this is officially shipped this extended property will therefore be deprecated.
More information can be found here:
http://documentation.red-gate.com/displ ... rations+V2
- Posts: 1124
- Joined: Mon Dec 05, 2005 4:54 pm
- Location: Twitter: @dtabase
Return to SQL Compare 10
Who is online
Users browsing this forum: No registered users and 1 guest