title: Continuous Integration and Database Management
body: <p>When working on a project with several other people it's common to have several people with differente areas, such as the database. </p>
  
  <p>My challenge is how to let several people edit the database model in a continuous integration environment. </p>
  
  <p>A developer has suggested writing a "versioning script" where each edit was entered into a .sql script, with a version-number that the database would be able to detect. A new addition to the model would in this file be tagged with a version, and the database would be updated once the script had been submitted and a build had been run.</p>
  
  <p>I've also heard about Publisher/Subscriber... and read a bit about it.</p>
  
  <p>How do you manage this situation in your daily work, and what suggestions can you give me to make the database-changes run as seamless as possible ?</p>
  
  <p>** Edit **</p>
  
  <p>Migration frameworks and migration-scripts have been mentioned. If you have some practical experience and would suggest a framework, that would also be appreciated.</p>