A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.
Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace
We have occasions where a multiple developers have multiple commits on what they are working on. For example
Dev1 - commit rev1
Dev2 - commit rev2
Dev1 - commit rev3
Dev1 - commit rev4
Dev2 - commit rev5
Under SQL Compare I cannot select all the commits for Dev 1 for SOURCE Control as my source, i have to do 1 by 1. Unless I am comparing the Database to Database but then I will see commits that I dont need for a particular deployment.
Is there a way to group Commits by via a Changeset or being able to select which commits i need instead of comparing 1 at a time.
- Posts: 34
- Joined: Mon Nov 21, 2011 9:55 pm
- Location: Atlanta, GA
Hi, thanks for your post.
I don't believe there's any way to do this. Each commit gets its' own revision number as you know, and there's no easy way to look at multiple ones of these at once. This is because, following your example, the same object could have been changed in multiple commits not only by one dev, but several. As the histories are cumulative, the later one would include earlier changes but of course it does include things from other devs if they committed in between.
In an ideal world each dev would commit at the end of a given job so that all the work for a certain task is grouped in one commit... but I do appreciate that's not always going to be practical.
- Posts: 1144
- Joined: Wed Jun 16, 2010 11:10 am
- Location: My desk.
I'd be interested in knowing why you want to just take the changes for Dev1 and specifically not Dev2.
- Posts: 1124
- Joined: Mon Dec 05, 2005 4:54 pm
- Location: Twitter: @dtabase
Return to SQL Source Control 2
Who is online
Users browsing this forum: No registered users and 0 guests