Environments and Branching

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

Environments and Branching

Postby robert_biddle » Wed Oct 19, 2011 12:40 am

Hi, I'm very interested in purchasing the RedGate source control product for my development team. However, I'm struggling on formulating a strategy for managing environments and branches.

We basically have Dev, Test, QA, Staging, and Prod environments. We already have TFS but I'm especially interested in RedGate source control because it appears very easy to use and it integrates well with SSMS.

What do most users commonly do to manage their environments?

My initial thoughts were that we'd have Staging be the main trunk while Dev, Test, and QA would all be branches. As changes move from Dev to Test then we'd merge the specific changesets.

Does this sound like the right approach?
robert_biddle
 
Posts: 2
Joined: Wed Oct 19, 2011 12:17 am

Postby Chris.Allen » Fri Oct 21, 2011 10:39 am

Basically, you need a separate folder in TFS for each database. To merge changes from one step to another, you could use SQL Compare directly between the DBs and then commit all the updates back in rather than doing it through TFS and a Get Latest, as it'll handle all the dependencies correctly etc.
Chris.Allen
 
Posts: 594
Joined: Thu Mar 12, 2009 4:17 pm

Postby robert_biddle » Sat Oct 22, 2011 1:55 am

I think that should work out quite well. I used to do something similar with Schema Compare in TFS between DB Projects but there were some occasional issues. I'll give it a try. Thanks!
robert_biddle
 
Posts: 2
Joined: Wed Oct 19, 2011 12:17 am


Return to SQL Source Control 2

Who is online

Users browsing this forum: No registered users and 0 guests