title: Database versioning when using continous integration
body: <p>I have an odd situation where there is a SQL server database used by atleast 4 different applications and there are 4 different teams working on each of these applications. </p>
  
  <p>We are planning to bring in continous integration using TFS 2012 across all these development teams. </p>
  
  <p>Now there is no problem on managing the code for these applications, the problem is on managing the database changes and maintaining versions. 
  <strong>The main challenge however is each team can have their own set of changes on the same database.</strong></p>
  
  <p>The objective is at a given point I should be able to collect artifacts (for both web and database changes) for all the 4 applications and deploy them to staging or production environment.</p>
  
  <p>Please advice!</p>