Do changes have to be applied in order?
SQL Source Control increments a Revision number after each change. Does this imply that I am required to apply all changes up to a given Revision in a second database? I really want to apply only selected changes, and in my own order.
RELATED: If I select Revision 10 to apply to my database, and then select Revision 7, have I effectively removed changes for Revision 8, 9 and 10?
Note that I am most concerned about DATA in these cases. The schema for this particular project is mostly stable. I'm just trying to keep track of data rows that determine program functionality (data-driven application).
If you use SQL Compare to apply changes from a particular revision, you can always uncheck any objects you don't want to push to your target database. The drawback is that your target database will be inconsistently versioned, set to a hybrid of multiple revisions. This might make it hard for you to manage changes in the longer term. With data changes, I can't see why you can't selectively take records using SQL Data Compare.