title: Database Deployment Strategies (SQL Server)
body: <p>I am looking for a way to do daily deployments and keep the database scripts in line with releases. </p>
  
  <p>Currently, we have a fairly decent way of deploying our source, we have unit code coverage, continuous integration and rollback procedures.  </p>
  
  <p>The problem is keeping the database scripts in line with a release. Everyone seems to try the script out on the test database then run them on live, when the ORM mappings are updated (that is, the changes goes live) then it picks up the new column. </p>
  
  <p>The first problem is that none of the scripts HAVE to be written anywhere, generally everyone "attempts" to put them into a Subversion folder but some of the lazier people just run the script on live and most of the time no one knows who has done what to the database.</p>
  
  <p>The second issue is that we have 4 test databases and they are ALWAYS out of line and the only way to truly line them back up is to do a restore from the live database. </p>
  
  <p>I am a big believer that a process like this needs to be simple, straightforward and easy to use in order to help a developer, not hinder them. </p>
  
  <p>What I am looking for are techniques/ideas that make it EASY for the developer to want to record their database scripts so they can be ran as part of a release procedure. <strong>A process that the developer would want to follow</strong>.</p>
  
  <p>Any stories, use cases or even a link would helpful.</p>