title: Versioning SQL Server?
body: <p>My development group uses Visual Source Safe for version control; this choice was originally made due to cost and its tight integration with Visual Studio.</p>
  
  <p>As our repository has grown Source Safe has really started to show its limitations and we are considering moving to another solution.  Up for discussion are Team Foundation Server, Subversion, Git, and Mercurial.</p>
  
  <p>We are largely a data shop, so another major factor for us is being able to easily version SQL Server 2005/2008 projects.  This is one of the benefits of using Source Safe, and also of Team Foundation Server - the integration with Microsoft SQL Server Management Studio.</p>
  
  <p>I'm wondering if anyone has had experience versioning SQL Server with Subversion, Git, or Mercurial and can provide some solid pros/cons for each of these systems, as well as how you went about implementing them.</p>