Moving database changes to staging in a multi developer environment

I've done this a few different ways, but I was wondering what other people do out there...

Situation is this:  Business application with a Sql Server Database, using VS.Net 2003.  Small development shop, which means all developers may be working on changes that need to go to the staging database at some point.

How do you manage the changes going up and down the line from development to staging?

I am looking at the VS.Net database project type and it really looks promising, but I am curious what other people are doing...

posted on Wednesday, November 24, 2004 4:02 PM

Feedback

# re: Moving database changes to staging in a multi developer environment

We use a vs.net DB project and have had pretty good results with it. The versioning part has been wonderful during new development, but as we get into maintence mode there have been a few issues keeping track of what's current, and whats in process. This could of course be handled with branching, which is our final solution, but for now we use 2 DB projects, 1 for the developers, 1 for the DB folk, and the DB folk move what needs to be rolled to releases to their own project on word from the dev staff. This also gives the DB staff the implcicit ok to QA the db work, which is a nice step we will lose with branching, which we will have to work out at that point. All in all, though, I wouldn't want to manage the DB without the DB project, or something like it anymore.
11/25/2004 12:20 AM | Aaron Junod

Post Comment

Title  
Name  
Url
Comment   
Please enter the following code into the box below to stop spammers

   		Enter Code Here *