title: Databases and DVCS
body: <p>I've recently asked a question about how suitable a DVCS is for the corporate environment, and that has sparked another question for me. </p>
  
  <p>One of the plus sides to a DVCS seems to be that you can easily branch and try out new things. My problem starts when I begin to think about database changes. I've always found it tricky to get a DB into a VCS and it just sounds like it's going to be even harder with a DVCS.</p>
  
  <p>So, whats the best way to work with databases and a DVCS?</p>
  
  <p><strong>EDIT:</strong> I've started looking into Migrator.NET. What do people think of projects like this for easily moving between versions specificaly with experimental branches in your DVCS?</p>