How do you manage your DB development projects
-
Hello all, As per the title I am curious to learn how, from a source control/versioning perspective, other people manage DB development projects? As an example I am currently managing a large project with around 20 developers. This project is primarily developed in C# and VS 2005 and sources are stored/versioned using Subversion. Now this all works for the source, but it doesn't quite fit when it comes to controlling the DB. Currently we have a "DB Scripts" project, that contains all the scripts needed to build a DB from scratch and these are checked in/out using Subversion. However it is a tad cumbersome. BTW this is all for SQL2005
-
Hello all, As per the title I am curious to learn how, from a source control/versioning perspective, other people manage DB development projects? As an example I am currently managing a large project with around 20 developers. This project is primarily developed in C# and VS 2005 and sources are stored/versioned using Subversion. Now this all works for the source, but it doesn't quite fit when it comes to controlling the DB. Currently we have a "DB Scripts" project, that contains all the scripts needed to build a DB from scratch and these are checked in/out using Subversion. However it is a tad cumbersome. BTW this is all for SQL2005
We are a much smaller shop, 5 developers, but we use SQL Compare from Red-Gate for deployment, Source safe for source control (this is very unsatisfactory). We expect to move to Team foundation server soon. SQL Compare is bloody marvelous. User signs off on UAT DB and it is deployed to production with no problems. Managing the development cycle is more challenging. When there are changes in UAT and the users want to start another round of changes cn be a nightmare!
Never underestimate the power of human stupidity RAH